Hi Kamal,

Thanks for your suggestion. The current download of lookup tables takes less than 1 minute. Not even enough time for the user to go for coffee. But I'll keep your suggestion in mind if the download gets slower.

Paul

>Hi Paul,
>
>Simply, retrieving the updation timestamp and primary keys would be a better option. (i.e. only if your lookup tables have lots of fields)
>
>You can compare these timestamps against your local table's, and issue SQL update for updated ones, SQL DELETE for deleted ones and a loop with INSERT for new ones. This looks like more work and even more SQLs but still it will be a little faster as everything is done on the local machine.
>
>If you have just a couple of fields in the lookup, don't even bother to do such a thing. <g>
>
>>Hi Nabil,
>>
>>>
>>>Do you store the lookup tables on every client machine?
>>
>>Yes.
>>
>>>How do you regularly update these tables on the client machine?
>>
>>After the user logs on, I display a download of lookup tables screen. The screen allows the user to download all or some of the lookup tables. The user can bypass the download entirely if his lookup tables are up-to-date.
>>
>>If you want my code to update local lookup from MSSQL Server, let me know.
>>
>>Paul de Niverville