Is it possible to develop one ADP application and use it both for SQL and MDB backends? In some locations, we will have SQL servers. In others, they are stand-alone machines. I would like to only maintain one copy of code - even if it means doing some:
IF SQLCONNECT do this.... make date delimiters ''
IF MDBCONNECT do this.... make date delimiters ##
etc.
I have the ADP setup to use a DSN file for the SQL server and that works fine. I have a DSN for the MDB also. That is giving me some problems. Before I spend time working out the problems, I just wanted to know if anyone else is doing this? Can you link the tables via code each time the ADP is open? With the SQL DSN, the ChangeConnection sub I'm using just makes all the tables in the database show up.
/Wendy
IF SQLCONNECT do this.... make date delimiters ''
IF MDBCONNECT do this.... make date delimiters ##
etc.
I have the ADP setup to use a DSN file for the SQL server and that works fine. I have a DSN for the MDB also. That is giving me some problems. Before I spend time working out the problems, I just wanted to know if anyone else is doing this? Can you link the tables via code each time the ADP is open? With the SQL DSN, the ChangeConnection sub I'm using just makes all the tables in the database show up.
/Wendy