I wrote a batch file that upon open of the FE checks the version of the
client to that of the server and if it is not up to date it copies over the
new client, everything works great except for the fact that I have linked
tables. When the client opens I have to select the machine data source for
every linked table and enter my user name and password. This is such a pain.
I tried pass through queries but they are read-only and do not work in
subforms or subreports as I have.
I tried connecting programmically through the start up form on Access with
the connection string in there but that didn't work either.

Anyone have any suggestions?

--
Message posted via http://www.accessmonster.com

See whether going DSN-less helps. I show one approach at
http://www.accessmvp.com/DJSteele/DSNLessLinks.html (You'll have to check
Carl's site for the appropriate connection string)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"nwilliams via AccessMonster.com" <u31367@uwe> wrote in message
news:6fc6212a093cc@uwe...
>I wrote a batch file that upon open of the FE checks the version of the
> client to that of the server and if it is not up to date it copies over
> the
> new client, everything works great except for the fact that I have linked
> tables. When the client opens I have to select the machine data source for
> every linked table and enter my user name and password. This is such a
> pain.
> I tried pass through queries but they are read-only and do not work in
> subforms or subreports as I have.
> I tried connecting programmically through the start up form on Access with
> the connection string in there but that didn't work either.
>
> Anyone have any suggestions?
>
> --
> Message posted via http://www.accessmonster.com
>