It really isn't a speed issue.. it's a data management issue. It's easier to revert changes and IMO you're less likely to have data corruption. The user also has to get used to working with only a subset of the data. They'll need to query for a specific record, or all customers in Utah, or those that had purchases during the month. However, I've found that users generally think this way and they don't have a problem making the transition.

>Thats another question... views.
>Just in terms of speed talking, I notice that the table (as in any SELECT command in VFP) opens the "Master" table itself, so... whats the benefict in terms of speed ?
>(in opposite to the table it self and good indexs ?)
>
>Thanks
>(and sorry for my "novice" skills)
>(and my poor English :-D )
>
>>In addition to what Hilmar told you, use Views.
>>
>>
>>>Hi
>>>
>>>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.
>>>
>>>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.
>>>
>>>(any sugestions, samples and so on would be great)
>>>
>>>TIA