There is always a good reason.

Too bad that your start up app couldn't call a VB wrapper to do that for you in the background? Are these updated frequently, or every so often?

Some look ups are very static, like States and Customer types.

Just an idea?

__Stephen

>This client server application uses a lot of lookup tables, so rather than bringing them down the wire, I'm storing them in a local DBC. If they get changed on the server, a trigger fires and increments a key. When the client apps starts it checks this key. If it needs to, it downloads the lookup tables and updates the local tables. I'm using a progress bar to show the user what is happening. I needed to put a slight delay in the scans so the progress bar wouldn't move to fast. Kinda silly, but looks real nice now.
>
>Charlie