Hi all - This is a question from the MS Public newsgroups that deserves some consideration. If you don't want to answer over there, I'd be happy to take the spam hits and post for you.

---

Melissa,

I can't answer your question, but I will ask around and see what comes up.

I'm really curious why the existing FoxPro application runs so slowly. How many tables? How big are they? How many users? Do they keep the FPW app open all day or open and close it often?

--
Cindy Winegarden


FROM microsoft.public.fox.vfp.web on 2000/11/16: "FoxPro Speed Question"

"Melissa" wrote in message news: 03c101c05011$969f43e0$4c862ecf@cpmsftngxa09...
I am tasked with helping a client put their FoxPro 2.6 database online. I used to work heavily with FoxPro a few years ago so I am very familiar with programming FoxPro on the client level. I am currently an ASP developer who normally uses SQL 7.

1) The client uses a this program that is backed with FoxPro 2.6 that they do not want to connect directly to the foxpro db with the newly proposed web application.

I think their concern is that since foxpro already runs very slow on their end when accessing it over their network that it would further bog down foxpro with the additional web connections to the database.

I was thinking that since you simply open/grab recordset/then immediately close the connection to FoxPro with ADO that this would not cause any additional loss of speed.

If this is not the case then please advise.

2) The other option discussed was to create a SQL Job that would import the FoxPro data once a day for use in the web application. But data input into SQL would then need to be input back into FoxPro which I am not sure exactly how to tackle this particular issue.

3) Can I use a FoxPro 2.6 dbf file with Visual Fox Pro driver when creating a DSN to the 2.6 database? When importing into SQL will it work with a 2.6 database?

Any help on this matter would be greatly appreciated.

Thanks,

Melissa Alamo

---