>The problem comes when your project is hard-coded internally as C:\MyApp and you try to run it on the network on F:\NetApp. The EXE which you placed on F:\NetApp will STILL look at C:\MyApp first.

But C:\MyApp won't exist on the user's hard drive. So it won't find it there, and it will look in the current directory, which is where it is. Other than the extra work of checking a non-existing directory first, I don't see why it would be a problem. It would be nice, though, if you could hardcode the relative path off the current directory, but I didn't see any way of changing the path. Is there?

>I suggested that keyword to search, because several of the discussions were on handling just the type of scenario you're looking for - how to handle opening and closing tables.

I'll have to take a look at it, then.

Thanks,