RE: Connect to SQL Server 2000 .mdb .adb

Tech-Archive recommends: Fix windows errors by optimizing your registry

When setting up the DSN you provided information for your specific login in
order to connect using the mdb database, when your users use the mdb that is
the access they are using, on the other hand the adp database uses the
security setup in EM for SQL server, to be more secure setup roles in EM and
add users to those roles that way you can continue to use the adp, the Books
Online option in SQL server will give you all the details to handle this task,

--
jl5000
<a href="http://www.joshdev.com";></a>


"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, 1 user was able to connect to the SQL tables using the .adb
> file after I gave her dbo owner permissions (this user has Enterprise Manager
> on her system which the other user's don't have. My understanding is that
> you shouldn't need EM or dbo owner level of permission to work with MS Access
> Project. I definitely don't want regular users to have that level of
> permission).
>
> Any thoughts as to what may be causing this?
.

Relevant Pages

  • Re: Database or Project?
    ... I just create a blank database, copy the mdb file to the ... On that PC you create an ODBC DSN and then use ... that to create links to the tables on the SQL Server (with code the links can ... cases passthrough queries which use the same ODBC connection. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: From .mdb to .adp database
    ... I decided to go on with adp project, and i have created a store ... But queries are different stories. ... In SQL Server, there are Views, Stored Procedures, UDFs. ... Also, when you decide to use MDB front-end, you can choose use MDB ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Upsizing design considerations
    ... reports, with a ADP, or mdb (actually, it should be mde, or a ADE when you ... you would LINK the tables to sql server, and NOT USE a adp (the reasons is ... the first two remote users ...
    (microsoft.public.access.gettingstarted)