Thanks for your reply. The reason I was leaning towards storing these lookup tables on individual workstations versus using remote views was to eliminate as much network traffic as possible. The one important issue that I did not mention was that this system will be accessed over a WAN at 14 different locations accross the country. I suspect at any given time, there will be approximately 25 - 30 users accessing the system. Since these lookup tables are used in pulldowns which are filtered by SQL statements to only active codes in add and edit modes and allows all codes to be seen when being used for aiding in creating dynamic queries, I was afraid that using views may slow down the system to much. Any additional thoughts would be greatly appreciated.

Thanks,

Greg

>Without changing the Oracle database (putting triggers in the set some sort of update rquired flag), it's going to be difficult and, maybe, not worth the effort. Is there a reason why you don't just have remote views on the Oracle tables and create indexes on the views at app startup?
>
>>I am writing a client server application that requires the use of 16 lookup tables that I would like to store locally on each users workstation or on a shared network drive. These lookup tables are fairly static an occupy less than a meg with index files. What is the best way to compare these local tables with the equivalent tables in an Oracle database. The intent is to only refresh the local individual table when the Oracle table has been updated. I would want to check if the tables have changed each time the user starts the application. Any suggestions would be greatly appreciated.
>>
>>Thanks,
>>
>>Greg
>>
>>P.S. Using VFP 6.0 SP3 and Oracle 7.3.3