>I'm trying to define the best aproach on a LAN based aplication...
>My question is:
>should a I open my tables and never close then (to speed up data operations) or in the other end, should I open tables just when I need them, since as I understand, Foxpro tables are fragile and could get damaged in a LAN failure.
1) Keep tables open for speed.
2) FLUSH for safety. Even TableUpdate() doesn't necessarily write changes to the physical disk. And make sure the server doesn't have write-cache.
3) Pay due homage to god backup. Otherwise, his vengeance will be upon you.
>I know I should use SQL Server as the best way of doing this, but I'm no expert and dont have that much time to get the proper training and do a SQL Server application.
I don't think it is justified to invest in SQL server just because of this. Of course, C/S has several advantages, that might make you want to use it eventually.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
