"gmead7" wrote:

> I figured this out so I wanted to share in case others encounter this. I
> created the .adb Access Project on my desktop which has SQL server installed.
> In Access Project, Under Menu, Connection, my server name appeared
> correctly. This worked great on the machines that had SQL already installed
> on them; however didn't work at all on other machines that did not. The key
> to getting it to work was to add a comma space then the port number of the
> SQL server after the name SQL server in this Connection entry.
>
> I'm hopeful that this discovery will be helpful to someone.
>
> "gmead7" wrote:
>
> > I recently moved my Access BE tables to SQL Server 2000. I re-worked my
> > Access front end .mdb to link to these tables through a DSN file. I got
> > daring and expiremented with .adb Access Project format. It worked great
> > except for when I tried to share it off a shared draft with other users. My
> > other users are able to connect fine with my .mdb Access file and the DSN
> > file on the shared drive; however, my users are not able to connect to these
> > same SQL server tables through the .adb file (which has the location of the
> > SQL tables defined within - it works great for me, but I'm the only one who
> > can connect up). These user's received "SQL Server does not exist or
> > access denied." Error message (but I know SQL server exists as I'm able to
> > connect with the .adb file and I know the other users have access as they're
> > able to connect to it through the .mdb file).
> >
> > 1 other note, 2 other users were able to connect to the SQL tables using the
> > .adb. These 2 users both have Enterprise Manager on their machines. I have
> > Enterprise manager on my desktop machine, but not on my laptop. I'm able to
> > connect with my desktop machine, but NOT my laptop. Do all my users whom I
> > want to connect via Microsoft Access front end need to install Enterprise
> > Manager on their machines? This shouldn't seem necessary and I definitely
> > don't want to do that. I've tried taking a closer look at MDAC type issues
> > and that doesn't seem to be the problem. Also, I need a simple way for this
> > to be resolved as the Front End Access Project users aren't IT technicians.
> >
> > Any thoughts as to what may be causing this? I appreciate all suggestions