I have an existing ClickOnce application that uses an Access database.
Recently I have determined that I needed to split the database into two components: System (tables that are maintained by me...the developer), and User (tables that the User has their data in...Client records/transactions, etc.).
I did this because I realized that when the ClickOnce was being installed as an update, some of the data in the Database (that I added as the developer) was not getting into the updated deployed database...
Conversely, I didn't want to clobber any existing data that the Client was working with when I needed to add some system records or new tables in the design.
So...I've split the existing database. Now however...I have a problem. Some of the user tables need to include some system table fields in some queries. I'm trying to find a way of adding the tables from the separate databases into a <dataset>.xsd (Data Sources definition), but I'm not having any luck going in that direction.
The other way is to simply link to the system tables from the user database, but when I publish/deploy the app, I'm sure that the link definition will not be correct and I'll get some sort of error at runtime saying that it can't find the table or the database.
They are both Access2007 databases and I'm doing this in VS2010 under VB.
Any suggestions would be greatly appreciated.
Paul Goldstein
Paul D. Goldstein Forceware Systems, Inc.