>... everything fell into place nicely for me without having to kludge method >code...

Kludge is such an ugly word. :)

Roxanne,
I was out of town when I replied to your message so I didn't really take as long as I should have. The reason I put code in the BeforeReadEvents instead of the appincl.h is to keep the program flexible.

The WAN and LAN's that we are designing for often allow users to access data in completely different ways. And that includes the paths. So instead the code in the BeforeReadEvents methods opens the metadbc and extracts the path for the core database and the common database. It then uses that information to set the proper path.

This works no matter how the system is set up. I was just recently in N.C. testing the system and that group didn't have full access to the WAN yet. So I simply changed the path that was stored in the MetaDBC and my system worked perfectly. They were working with data local to them and I only had to change two lines stored in a table without any other work. I don't think I would have been able to do that if the path was defined in the appincl.h, at least not with out rebuilding everything. This same technique also works with developers that are not attached to any network. They just remap the MetaDBC and suddenly they can test the system.

Of course once everyone is working on the same page (WAN) it would be faster for us to just use the appincl.h with UNC references. But for now we are limited to this method.

I hope this helps,
Bill