David W,

As an experienced reseller/modifier of Visual Accountmate since 1996, and a former SBT Reseller, I can tell you that I STRONGLY, STRONGLY urge you go with SQL or MSDE. Your arguments about VFP data being stable in a controlled LAN environment with UPS's etc. are valid - I have experienced the same. However, even in the most stable environments I have seen corruption from time to time. But that isn't the primary reason I believe you should go with SQL or MSDE. The bottom line is that Accountmate Software Corp/Softline has put the bulk of their development efforts into SQL, and they will continue to do so. As a result, the SQL product has less bugs (way less), more third party apps available for it, more native VM modules, better support,etc. etc. I understand your reluctance to go through the learning curve with SQL - I've been going through it myself for several years now. Also, consider that if you are the only person doing the mods it's one thing, but finding programmers with SQL experience is considerably easier than finding good xbase/vfp programmers at this point, I'm sad to say.

I would be happy to go over the design differences between VAM lan and sql with you - e.g. use of remote views (which 'kind of' insulate you from some of the difficulties of sql) - stored procedures, etc. I'd also be happy to act as a resource for you in helping you get through modifications, design issues, product knowledge etc. I can also help you with SBT, or others if you elect to go that way.


>My company is looking for a new accounting package. We have been looking into a few packages written in VFP, so that I will be able to customize it.
>
>I was disappointed to learn recently that only the SQL & MSDE versions of Accountmate will be marketed here in my country, by the Softline group. (The USA version is currently being customized for local VAT tax etc) The MSDE LAN version replaces the VFP table LAN version.
>
>I have written a few small apps using VFP and VFP tables, and am very comfortable with it. However, I know nothing about programming with SQL/MSDE. I am not really a professional programmer, and would hate to go through the SQL learning curve.
>
>All I can see is that MSDE would be a major learning curve. I would not be able to open tables, look at the data, add fields, create strings of commands, etc that I can presently do with VFP tables. I cannot visualize working “blindly” with MSDE tables, as opposed to the VFP database designer, where everything is graphical, where tables can be dragged onto forms as grids, etc. All my current knowledge of working with VFP tables would be lost.
>
>I can understand that SQL/MSDE has more security, and is less likely to encounter corrupt files. But for a small company with a LAN of about 10 computers, where security is not really an issue, where a UPS can help prevent power outages, I cannot see the big advantage of MSDE over VFP tables.
>
>If we were to grow to 20 or more users, VFP could easily handle the job, whereas with MSDE, the built in throttle would try to slow things down, in an attempt to get you to buy full SQL. SQL also seems to require constant administration. (Also, VFP only has 2 GB table limit, whereas MSDE has a 2 GB database limit.)
>
>I would imagine that there are many LAN (and even WAN) applications out there that run on VFP tables, some of them with 100 or more users, that do not give any problems.
>
>I see SQL/MSDE as a big clumsy expensive option, aimed at large organizations.
>I see VFP tables as simple, flexible, easy to use, and free.
>
>Aren’t VFP tables far easier and more flexible to work with than MSDE tables?
>
>On a local area network, is security & possible file corruption that much of a problem with VFP tables?
>
>Is it really necessary to replace VFP tables with MSDE tables in applications?
>
>Will VFP 8.0 databases and tables have any added features, or will that be withheld to protect SQL?
>
>
>Regards