Bill Feder
asked on
Access 2003 crashes on new server.
We have a fairly large access data base and are planing to move it over to a new terminal server machine. The data base has a front end and a seperate back end.
As always we had to make sure we have all the referances, which we do.
We are coping the front end to the new C drive and the back end to a new F drive. When the front end opens it will crash on a line code that is checking for any possible appointments for the particular user. If I remove the code then it will run as expected.
This is a 2003 access database and we are moving from a 2003 server to a 2008 R2 server.
What I don't understand is why this will run without any problems on the 2003 server and
fail on the 2008 server. Is there something different with the referances etc. etc.
As always we had to make sure we have all the referances, which we do.
We are coping the front end to the new C drive and the back end to a new F drive. When the front end opens it will crash on a line code that is checking for any possible appointments for the particular user. If I remove the code then it will run as expected.
This is a 2003 access database and we are moving from a 2003 server to a 2008 R2 server.
What I don't understand is why this will run without any problems on the 2003 server and
fail on the 2008 server. Is there something different with the referances etc. etc.
ASKER
Hi Jeff
Everything has been updated and compiled numerous times.
We have 10 machines that run the same front end without any problems.
If I make any changes in the front end I copy it to location where everyone else
can click on a button and update there front end. So in a sense there may be some
differance. I have been doing this for over 15 years so I don't think that is the problem.
I did not mention that this also happens on a windows 7 laptop that I use. I am thinking of taking all the referances from my machine and putting them on the new machine?
Thanks for your help.
Below is the code:
StrStatus = "open"
StrUsername = User_name
stDocName1 = "Appointments"
SqlAppointments = ("SELECT * FROM Appointments WHERE (((Appointments.Employee)=
' order by SnoozeFromDate
Set Mydb = CurrentDb
Set Myrs = Mydb.OpenRecordset(SqlAppo
If Myrs.EOF = False Then
DoCmd.OpenForm stDocName1, , , stLinkCriteria1
Else
If BlnShowTodaysSchedule = False Then
MsgBox "There Are No Schedule Events Today For" & " " & StrUsername
BlnShowTodaysSchedule = True
End If
End If
End If
Everything has been updated and compiled numerous times.
We have 10 machines that run the same front end without any problems.
If I make any changes in the front end I copy it to location where everyone else
can click on a button and update there front end. So in a sense there may be some
differance. I have been doing this for over 15 years so I don't think that is the problem.
I did not mention that this also happens on a windows 7 laptop that I use. I am thinking of taking all the referances from my machine and putting them on the new machine?
Thanks for your help.
Below is the code:
StrStatus = "open"
StrUsername = User_name
stDocName1 = "Appointments"
SqlAppointments = ("SELECT * FROM Appointments WHERE (((Appointments.Employee)=
' order by SnoozeFromDate
Set Mydb = CurrentDb
Set Myrs = Mydb.OpenRecordset(SqlAppo
If Myrs.EOF = False Then
DoCmd.OpenForm stDocName1, , , stLinkCriteria1
Else
If BlnShowTodaysSchedule = False Then
MsgBox "There Are No Schedule Events Today For" & " " & StrUsername
BlnShowTodaysSchedule = True
End If
End If
End If
...and what line is it crashing on?
You may not be able to simply "Take" a reference from one machine an put it on another.
These references and libraries need to be installed properly and may will not work correctly (or worse cause corruption) on machines that they may not be compatible with..
You may not be able to simply "Take" a reference from one machine an put it on another.
These references and libraries need to be installed properly and may will not work correctly (or worse cause corruption) on machines that they may not be compatible with..
ASKER
This is where it crashes SqlAppointments = (" in debug mode you can walk through it
and the following lines untill you get to If Myrs.EOF = So thats here it really crashes.
and the following lines untill you get to If Myrs.EOF = So thats here it really crashes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Make sure that all your Software is up to date and fully patched (Windows AND Office)
Run the compact/repair utility on the database
Compile any code (in the vba window, click: Debug-->Compile)
Run the compact/repair utility on the database again
Other questions:
Is this an issue for only this one user, or for all users?
Can you post the code, and indicate what line is crashing?
JeffCoachman