Re: Error opening report
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Tue, 14 Oct 2008 23:04:04 +0800
Good news. Sounds like some kind of corruption.
It could be to do with the user, or - if he uses the same machine - it may be something faulty in the network connection or in the hardware of that machine.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"David" <dkroll@xxxxxxxxxxxxxxxxx> wrote in message
news:c65c3da3-fb1b-42ff-a66a-d3ddbcf8d0c7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Allen,
Thanks for the suggestions. It's funny you ask about the printer.
This particular user used to use a Dell AIO 946 printer. He'd have
this same problem until I figured out that the printer was causing the
problem. He no longer uses that printer and I did try switching
default printers to no avail. The way this mdb works is that the user
has a local copy of the database and gets a new version from the
server if a newer version is available. I fixed the problem by
copying the version from the server to the client. I'm not sure if
this user accidentally hit a wrong key or button that could have
caused this problem, but it's fixed for now. Funny thing, it's always
the same user that has these problems.
Thanks again.
David
.
- References:
- Error opening report
- From: David
- Re: Error opening report
- From: Allen Browne
- Re: Error opening report
- From: David
- Error opening report
- Prev by Date: Re: dlookup - calculated field in group footer
- Next by Date: How can I put page breaks into an Access Report based on header?
- Previous by thread: Re: Error opening report
- Next by thread: RE: Error opening report
- Index(es):
Relevant Pages
|