vihaan
asked on
MS access report
Hi Whenever user tried to open the report. He is getting error called
"MSAccess.exe has generated errors and will be closed by Windows. You will need to restart the Program. An error log is being created".
So i asked user to send his database to me and I opened the same report when i recieved the database on my side. But All the reports were opening properly. I am not getting any such kind of error. Please help me. Thank You.
"MSAccess.exe has generated errors and will be closed by Windows. You will need to restart the Program. An error log is being created".
So i asked user to send his database to me and I opened the same report when i recieved the database on my side. But All the reports were opening properly. I am not getting any such kind of error. Please help me. Thank You.
David Kroll
Can you find the error log? Are you connecting to any ODBC data sources?
ASKER
No its not web based database. We do not have front end or back end . the user has got his own copy of database.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the report has got code only in NO Data event. Even there its just 4 or 5 lines of code which should throw up a dialog box saying No Data whenever the report has got no data.
I do not think there is anything wrong with the database. Because Everything seems to be working when i open the users database on my system.
I do not think there is anything wrong with the database. Because Everything seems to be working when i open the users database on my system.
dkrollCTN: Sorry about the crosspost!
No problem LSM!
ASKER
You guys think some thing is wrong the office on users system. And we should look at reinstalling the office.
That's a possibility. Try running the report on another user's computer and see if they have any problems.
ASKER
Yep I already tried. Another user has also got the same problem.
Maybe a permissions issue. As LSM asked, has the user been able to use this report before with no problems?
ASKER
Yes
Then something has changed, whether it's his Office installation or something else, something has changed.
<Yep I already tried. Another user has also got the same problem. >
Are these users running SEPARATE copies of the database, or are they sharing the same copy? With multiple users on the same network, you should have a Backend (data only) and a FrontEnd (everything else), and EACH user should have a separate copy of the FE (all FE's should link back to a single copy of the BE).
Is that the way yours is setup?
If not, then the first order of business is to split the database and deploy it as mentioned.
If the db is already split:
Do these users have a copy of the FE installed on their local drive, or are they running this from a network share? It's fine to have the BE on a share, but the FE should be installed on each users workstation.
Is this a standard, typical LAN-type network, or do you have users running this via VPN/WAN, wireless, etc? Access does not fare well under those circumstances.
Even with a typical LAN, you can have troubles if the network connection drops unexpectedly. Most often this results in data corruptiong, but depending on your setup you could certainly experience this sort of thing. Do all users who are having this trouble share a "common" point, like a router or switch?
Are these users running SEPARATE copies of the database, or are they sharing the same copy? With multiple users on the same network, you should have a Backend (data only) and a FrontEnd (everything else), and EACH user should have a separate copy of the FE (all FE's should link back to a single copy of the BE).
Is that the way yours is setup?
If not, then the first order of business is to split the database and deploy it as mentioned.
If the db is already split:
Do these users have a copy of the FE installed on their local drive, or are they running this from a network share? It's fine to have the BE on a share, but the FE should be installed on each users workstation.
Is this a standard, typical LAN-type network, or do you have users running this via VPN/WAN, wireless, etc? Access does not fare well under those circumstances.
Even with a typical LAN, you can have troubles if the network connection drops unexpectedly. Most often this results in data corruptiong, but depending on your setup you could certainly experience this sort of thing. Do all users who are having this trouble share a "common" point, like a router or switch?
Hi,
What operating systems are on your computer and your users?
What version of Access are you both using?
Is it only one report or the whole database that has this issue?
How many users are they?
How many have this problem?
Reinstalling office is a very good idea on your user side.
Would we be right in presuming that the tables, forms, reports etc are all in one database and you haven't split them out into back and fron ends?
Jim
What operating systems are on your computer and your users?
What version of Access are you both using?
Is it only one report or the whole database that has this issue?
How many users are they?
How many have this problem?
Reinstalling office is a very good idea on your user side.
Would we be right in presuming that the tables, forms, reports etc are all in one database and you haven't split them out into back and fron ends?
Jim
Compare other installed applications on both machines, yours and the his.
ASKER
My Database is not split. it does not have Back end and Front End. The users are experiencing this issue only when they try to open that specific report. Access versions are same But they might be having Service pack1 or 2 o3 . All the users at their workpace are accessing the same database put on their server. I could not think of anything that helps me in resolving this issue . I have one option in my mind , which is to reinstall the office. Please help me. Thank you for replying.
Ok, so when the problem occurs for the users, the db is on a server that they have access to, but when you test it, it is on a local pc and you access the db directly?
Can you get access to the server to try and open the report directly from there and see if the fault still occurrs? This will either eliminate the users machines and the mehtod they are using to access the db or narrow it down to that.
Can you get access to the server to try and open the report directly from there and see if the fault still occurrs? This will either eliminate the users machines and the mehtod they are using to access the db or narrow it down to that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
good