Distributing ADP's

[ainganni]

we are using an ADP as a backend admin tool for a web based application. the problem we have is that the ADP uses an interal ODBC style connection setting therefore when we set it up in th eoffice we are pointing it at out local database server, however this will not be the name of the server when the product is shipped. Microsoft very helpfully suggest you include instructions of how to change the connection settings, however it is not goign to inspire an end user with confidence if the very first thing they see is an error. So is there a way of setting up an access project to use a more traditional system DSN??

Any help is appreciated

thanks in advance

Andrew

 

[cmmrfrds]

What is the reason you need to use ODBC instead of a native OLE-DB connection?

 

[ainganni]

the ADP will be distributed, when we do this the name of the server is going to be wrong (even if we use localhost as the project is likley to be on a client), so that the end user is not presented with an error it would be better to set up a system DSN (which can be explained how to do) then hook the ADP up to the DSN, thus avoiding any nasty error messages

 

[markphsd]

When I did a distributed ADP, I set up an entry form; it had a listbox that you could select from the avalible servers, and then a list box that displayed the avalible databases for the selected server. You could set up default db's and servers, so that the user doesn't have to manage it, or a one time setup so that the entry form isn't bothersome, it also user name and password text boxes.

Look up the DMO in help.. i think it's DMO, i haven't looked at it in a while.


Mark P.

Bleh