-
[RESOLVED] Report Error
I have a button on a form that opens a report.
When the users in a certain location click this button they get an error saying the OpenReport action was canceled.
I don't understand why they are getting this error. I logged into the server as myself that they were running the program from and the button open the report fine. I even logged into the server using the user's login and the report runs fine.
I tried putting them on different servers and they still get the same issue. I even tried deleting the .MDB and creating a new one and the error still persiss only for them.
Any idea why this problem is specific to them?
-
Re: Report Error
What Reporting are you using? Did you install the program on their systems, on the server, or just copied it over?
-
Re: Report Error
I think you need to sit down with them, at their desk, and show you what they are doing.
-
Re: Report Error
The program and report were created using access.
The program is on a server and they click on an icon which runs the program from the server.
They're in another city, but I did shadow them and I went through it myself and I see the error they are getting.
But, like I said I ran it with different usernames where I work at and it works fine.
-
Re: Report Error
When they start up the db are the macros enabled?
What server are you "shadowing" them with. Usually shadowing is for Terminal server or Citrix.
So they are running the app on the server or are they just executing a shortcut on their systems and the db is located on the server?
-
Re: Report Error
Macros are enabled.
Using Citrix.
They go to Citrix Neighborhood on their system where it lists all the programs we have for them to use. When they click the program is runs the program which is located on several servers.
-
Re: Report Error
Is there a another query to some other database or data source? Can you post some of the code?
-
Re: Report Error
I just recreated the report using Access 2000 and now it seems to be working. These access 2000 programs are being run by the user from new servers which have Access 2003. The only thing I can think of is some how with the upgrade all the settings aren't pulling correctly.