Visual FoxPro???

Hello All,

Well I'm not sure that this is the right forum but i've got a general question about Visual FoxPro.

Visual Foxpro is distributed with Visual Studio right. What are the differences between developing in Visual Foxpro and Access. Is one alot better (more poweful / easier / faster / etc.) than the other? I know a fair bit about Access but not Visual Foxpro.

I've been asked to assess the feasability of porting a Visual Foxpro database system to Access. I don't know (and neither do the people who asked me) if this is worthwhile to do or not. Thats why i want to find out more about the differences between the 2.

I've looked for info on the net but havn't found any good comparisons of the 2.

Any info or opinions would be great.

Thanks

Mark

Foxpro was developed by Rushmore Technology as a dBase clone. Microsoft brought it because of thespeed of the search engine then available.

Foxpro is meant to generate compiled database apps whereas Access was initially designed as a desktop database applications.

If you are using vb/access then convert the Foxpro database to access, l think you can import it. That way you cut down on the number of application types you have to maintain. The real cost of software is in the maintenance cost to the business user.

Foxpro is superior to Access in generating Business Modules, wherease Access is meant for more personal desktop databases.

thanks for the info jethro,

i was looking at the msdn stuff for visual foxpro and it *seems* to be more powerful - like you say it can make separate applications - distributable etc.

I like your signature re johnny h.

I currently did a foxpro project for a company that formaly used access.
Foxpro is more powerfull but is a headache to use once you have gotten used to access.
VB apps work better with access.
I recomend sticking to access.
As far as I know access 2000 lets you run seperate apps.
But I'm not sure.
Dan.


[Edited by danab on 06-27-2000 at 10:36 PM]

Not sure about 2000.

We switched from dBase to Foxpro, which wasn't such a hassle, but then made the move to vb/access/sql which was way better.

FYI

Access 97 has a 1 gig limit to db size, 2000 has a 2 gig.