Hi Dragan

>No idea as to where things may have gone wrong, but if you have a views-only dbc, you can give each user a copy - you already have the code to create it from scratch, so why not do it on user's local directory? The app would be a tad faster, too, because every time you open a remote view, they hit the dbc; now they'd hit their own.

Yes, there is a views-only dbc and this dbc is on the local machine, the app starts locally using the local views-only dbc. I am using CodeBook as the framework so that is the way it was designed.

>The time to create a dbc may not be negligible - YMMV. Eight years ago, when I last had such a problem, I set the code to make new local dbc whenever the loader detected a new version of the exe, so it would be part of a "you have a new version, let me make sure your settings apply to it" bit of the installation routine, so the extra dozen seconds (or up to a minute on the then 200MHz machines and big DBF files) weren't confusing the user.

Yes, thanks for the idea. I have a flag zero byte file, which if found, the apps goes on to recreate the dbcs, then delete the file. I think just making it read-only will get the job done. Every time the app starts the dbc is recreated, not a big impact I am sure.