[AccessD] Converting to MySql

Rocky,

I don't think prompting them for the DSN parameters would be too good.

It sounds like Bruce has got some clues about creating a DSN as part of 
your application installation.  You would also have to include the 
installation of the ODBC driver as part of your installation as well. 
So perhaps you could explore further down that track, and maybe Bruce 
can provide some more specifics.

Otherwise, you would have to give instructions to them to set up the DSN 
themselves - and those instructions would include them giving the same 
name etc to the DSN as the one you used.  But then, I suppose the 
location of the MySQL database would be different for each user, so 
maybe you would have to set up a process for them to enter this in 
(server, password), and store it in a table, and get your code to refer 
to this.

Sorry, I didn't realise it was a distributed application.  This seems 
such a specific requirement, so I assumed it was part of a customised 
solution for a particular user.

Regards
Steve


Rocky Smolin at Beach Access Software wrote:
> This is a distributable product.  Do you think it would be better to force
> the end user to use my hard-wired DSN or allow them to create their own and
> prompt?