Windows 2003 server and Access XP

  • Thread starter Thread starter John Jahnsen
  • Start date Start date
J

John Jahnsen

We have upgraded from NT 4.0 and Windows 2000 terminal servers to Windows
2003 and Windows 2000 terminal servers.

On our earlier installation, Access was running fine.

After upgrade, access will not allow changing of database layour, if any
other user is using acccess on an other database.

We also have a limited access for 3-4 users in one database, earlier all of
us was able to use access at the same time.

Anyone know what is wrong, pls help.


John

(e-mail address removed)
 
You don't mention what version of ms-access are you are using.

However, you seem to state that:

Multiple users can work fine and use the database system and application
that you wrote.

However, you are stating that you can't modify forms and reports etc while
users are working in the he system? This ability was lost after access 97.
However, there is a not competent developer on the planet that would develop
and modify a live production database with users in it anyway.

So, the solution is to split the database into a code/forms/reports part,
and a have the backend as a data ONLY part. If you do this, you will
increase reliability of the system by a large amount...and also be free to
develop, and modify the "front" end application as you please...even while
other users work happily all day long.

For info on splitting...check out:

http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm

If your problem is that only ONE user can get into edit data...then you want
to un-check the "exclusive" option in ms-access when you open the datafile
(if exclusive is set..then only one user can get into the database). I
mention this issue, as it is not clear which of the above possible two
problems you have.
 
I dont think you understand what i wrote.
We are aware that you are not able to edit an open database.
What we try to say is that we are not able to edit if access is startet in
another users session, and working with a second database, not the one we
are trying to edit.

If you take a look in the name on the thread, you see that i wrote "Access
XP"

This is a problem regarded to our upgrate from nt server to windows 2003
server.

None of these problems occoured when using NT 4 as server.
Access have not been reinstalled, and the databases are the same.


John
 
John Jahnsen said:
I dont think you understand what i wrote.
We are aware that you are not able to edit an open database.
What we try to say is that we are not able to edit if access is startet in
another users session, and working with a second database, not the one we
are trying to edit.

If you take a look in the name on the thread, you see that I wrote "Access
XP"
Click to expand...

Gee, sorry, I did miss that you are using XP in the subject line! (my fault)
Access have not been reinstalled, and the databases are the same.
Click to expand...

Hum, ah yes, then are you running a separate box with terminal services? Ok,
then I assume the terminal server box is separate box from the new 2003
server.

I will say that as a general rule, you still must have each user get their
own front end, and this ALSO INCLUDES when you run terminal services. So,
each user STILL must get their own front end (that resides on the Terminal
Server session for each user). So, we don't allow multiple users into a
single front end...regardless of TS or not!)

However, this front end issue is a separate issue then your current problem.

Since you state that your Terminal services box was NOT changed, then
perhaps the licensing server part on the new 2003 server is not allowing
this? Which box is running the licensing server? This could very likely be a
licensing issue? I am not sure if you can, or do run the licensing server on
the same box as the TS box? You might want to check the licensing server
options, or even post a question in the TS newsgroups.
 
Back
Top