VFP 7.0 Database vs SQL Server

[Persmd]

I'm just finishing a standalone application using a database that contains about 200 objects. Word has just come to me about using it on a WAN. The application was written to allow file sharing, so concurrent use of the tables is not a problem. However, no "local views" were created, so "upsizing" my prototype database to SQL Server may be more difficult than if I had used views.

My questions are:

1. What are the ramifications of 300 users attempting to concurrently access a (native) VFP database?

2. Can more that 1 table within a VFP Database Container approach the 2 gigabyte table size limit, or is that limit imposed on the database too?

3. I Recognize the benefits of upsizing my prototype database to SQL Server, but my current application uses no "views" for selecting data. How inefficient would the result be (and is it possible) to migrate my current application into a client/server application without creating any "local views" first?

Any suggestions would be appreciated here.

Michael

 

[craigber]

300 simultaneous users. hmmm.. depends on what you are doing. If mostly doing queries you should be ok. With inserts and updates, you may be pushing it.

Now, having said that, performance on a WAN will be terrible no matter what you are doing. The difficulty on migrating to SQL Server depends on how you created the application. You aren't using views, which adds some complexity. If you use SEEK and LOCATE to find data, you'll have to replace all that with SELECT. Everything in SQL Server is done via SQL statements.

The 2 Gig limitation is per file...that is the DBF is one file, the FPT another. Same applies to the database container.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[Persmd]

Thanks Craig. Your answer is about what I had expected.

There was such a rush to convert an existing FoxPro 2.6 app to 7.0 that caution was thrown to the winds.

You know the old saying:

"There's never enough time to do it right,
but there's always enough time to do it again..."

Michael