J
Jan Il
Hi all,
Not sure anyone may be interested, or even come back this far, but, in case
someone else may have a similar situation, I'm gonna post the solution I
found back here to keep it all in one thread
After some lengthy research of all the generous responses and suggestions
I've received in reference to this problem regarding References, queries,
tables form controls, and an additional suggestion from Dirk Goldgar that it
might possibly be a printer related error, I have finally now found the
problem and a solution. Due to the type of error messages I was getting,
and finding that all the reports would open in both design and preview on my
work computer with Access 2000, but, would not at home with my upgraded
Access 2002 XP Pro, and Dirk's suggestion. I decided to satisfy my curious.
Being very determined by nature, I got to digging in a bit deeper and doing
some research and testing with the printer situation.
At work I have a HP 4100 series LaserJet as the default printer, and use the
4100 PS. At home, I have a HP G55 OfficeJet All-In-One. In view of the
continued errors I was getting with reference to the printer when I tried to
open these reports on my home PC, I decided to download and install the
printer drivers for the HP 4100 series to my computer. I then rebooted,
then added the printer to my selection list, and set it as the default*
printer.
I then opened the database, selected the new printer in my File | Print
setup. Then tried to open one of the errant reports in design view. Bingo!
Then tried preview...Shhazzamm!! I tried all the others that would not open
before, and they all behaved normally. To push the envelope the rest of the
way, I then reset the HP G55 as the default printer, then reselected it in
the DB File | Print. I compiled and closed the DB, then opened and tried
the reports again. All still behaved normally. <VBG>
I don't know if this is something I will have to do every time I want to
work with these particular reports at home, which is not all that often,
but, at least it is easy enough to work with, and I won't have to redo them.
;-))
What a gray-matter exercise...such a head rush! Whew!
My sincere thanks to all who were so kind and generous to give of their time
and assistance with this issue. I really do appreciate it. This was a very
good learning exercise for me too, given all the research and
troubleshooting involved.
Very best regards to all,
Jan
Not sure anyone may be interested, or even come back this far, but, in case
someone else may have a similar situation, I'm gonna post the solution I
found back here to keep it all in one thread
After some lengthy research of all the generous responses and suggestions
I've received in reference to this problem regarding References, queries,
tables form controls, and an additional suggestion from Dirk Goldgar that it
might possibly be a printer related error, I have finally now found the
problem and a solution. Due to the type of error messages I was getting,
and finding that all the reports would open in both design and preview on my
work computer with Access 2000, but, would not at home with my upgraded
Access 2002 XP Pro, and Dirk's suggestion. I decided to satisfy my curious.
Being very determined by nature, I got to digging in a bit deeper and doing
some research and testing with the printer situation.
At work I have a HP 4100 series LaserJet as the default printer, and use the
4100 PS. At home, I have a HP G55 OfficeJet All-In-One. In view of the
continued errors I was getting with reference to the printer when I tried to
open these reports on my home PC, I decided to download and install the
printer drivers for the HP 4100 series to my computer. I then rebooted,
then added the printer to my selection list, and set it as the default*
printer.
I then opened the database, selected the new printer in my File | Print
setup. Then tried to open one of the errant reports in design view. Bingo!
Then tried preview...Shhazzamm!! I tried all the others that would not open
before, and they all behaved normally. To push the envelope the rest of the
way, I then reset the HP G55 as the default printer, then reselected it in
the DB File | Print. I compiled and closed the DB, then opened and tried
the reports again. All still behaved normally. <VBG>
I don't know if this is something I will have to do every time I want to
work with these particular reports at home, which is not all that often,
but, at least it is easy enough to work with, and I won't have to redo them.
;-))
What a gray-matter exercise...such a head rush! Whew!
My sincere thanks to all who were so kind and generous to give of their time
and assistance with this issue. I really do appreciate it. This was a very
good learning exercise for me too, given all the research and
troubleshooting involved.
Very best regards to all,
Jan