HELP PUTTING ALL TO GATHER

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Ah! I am done upsizing my access database to SQL. Works great!! I transfared
it to my server which is Server 2003 and it works I used the trusted
authantication and thus no logging in is required for me. Now 2 problems: the
rest of the clients cannot use it. It says there are not connected. WHY? and
two what do I install in the clients to allow the whole thing to work the
same way it did in jet. In jet I had a back end tables and all the forms and
reports installed in all the clients. There is no split database in SQL.
HELP!!
 
If you are using a mdb file with ODBC linked tables as your frontend to
SQL-Server, you should ask this question in the newsgroup
m.p.access.odbcclientsvr; as this newsgroup is about ADP and has nothing to
do with MDB files and ODBC linked tables.

In your case, I would suppose that your users have some kind of
authentification problem with SQL-Server but you say nothing about that in
your post. While reposting, you should provide these details.
 
I will try again. The program was in access jet. I upsized it to ADP. I then
copied it to my server (small business 2003) All the clients are connected to
the server as users (The program allows me to connect to it as long as I am
logged in the client computer but it will not allow any other user who is
logged in, even in the same client computer). I would like them to use this
ADP upsized program. It has all the tables and forms and reports in it now.
What I do not know ( being new to SQL) is how do I let the program know that
the user is legit and allow them to connect to it. 2. What is the best
practice at this point for my program which is a very big program in terms of
speed and security. I appologise for the previous entry. I hope this helps
 
Oh, in this case, the solution is easy: each user must have its own copy of
the ADP file. The idea of opening the same file located on a server doesn't
work because when you open an ADP file, you automatically open it in design
mode and only one user can open an ADP file in design at a time.

It's exactly the same with a MDB frontend: each user must have its own copy
of the frontend; nothing change in this regard when you have an ADP
frontend.
 
Back
Top