I have a project that has been in beta and as such using a single "sandbox" library. The BO's are all mapped to tables in this library and they were the tables we wanted to update in development and testing. The library for our purpsoes was called DEVELOPMENT.

We are in a new stage of the project and the customer wants to use different libraries. I will call them PRODUCTION and TEST. He wants the BO's to map to PRODUCTION to pull the data structures and he wants the application to execute against the data in TEST. This seemed reasonable, I have plenned for this by having all my BO fills and updates flexible to take a library name from a shared property that is updateable via a menu option. This works fine for everything but the core update/add/delete functions, they are executing against PRODUCTION. I can see this in the data debug files.

It looks to me like the SF DB2 Client pulls the library name as a readonly property called TableSchema in the BO's designer file and it is indeed using PRODUCTION, which makes sense as the partial class is created by the BO Mapper which knows nothing about TEST.

So... am I right, and if so is there a workaround other than to manually update that property after each rebuild of the BO partial classes?

Keith Chisarik