2003 code raises error in 2007

[Kate]

Gina,
I think you are correct, that this was upgraded from Acc97.

I am using a common dialog control.

As to which objects caused errors, I can't recall. However, I'm in the
process of configuring an extra
computer as a test machine for Office 2007, so when I get that set up I
will perform this test and let you know!
(tomorrow sometime).

 

[Gina Whipp]

Kate,

Okie dokie...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Gina Whipp]

She already did... but it was an image... She will be starting to remove
the *useless* and no loger ones tomorrow.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Kate]

Yes, thank you both for getting involved. I am presently downloading a
slew of updates to
the old computer which I'm making my 'test office 2007' machine, and
after that completes,
I will jump back into this discussion. Stay tuned, and thank you!

-Kate

 

[Kate]

Okay, this is what I've done to address the code errors I was receiving
trying to run my Access 2003 applications under Access 2007:

I installed Office 2007 on a test machine, leaving Access 2003, Excel
2003, and Word 2003 intact. That was the first step.

My test machine, albeit an old PC with only 512 mb RAM, opened my Access
2003 mdbs without problems, in Access 2007. All functionality was there.
I unchecked the unnecessary reference to VBA extensibility, and still
not a hitch.

I then attempted to open the very same mdbs on the first machine, where
I had installed Office 2007 with the option to remove all previous
versions of Office,
and had the same problems as before.

I then removed Office 2003 from the test machine, and then tried to open
the mdbs in Office 2007. Turns out, Office 2007 has to
practically reinstall itself when you remove a previous version after
the original installation.

Anyway, the mdbs opened just fine after rebooting. We are coming to the
conclusion here that the first machine, where the errors still occur, is
having problems
caused by CLONING the hard drive to the new machine (this happened last
month), not by anything that Office 2007 is doing.

Thank you all for your diligent support!
-Kate

 

[Gina Whipp]

Kate,

No... THANK YOU for all YOUR hard work. You have enabled us all to know
that it is not an Access problem.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Kate]

Thanks for that link. I have saved it for future reference, as I think
this will not be the end of it...

I wonder if the installation procedure for Office 2007 does an excellent
job of removing all previous versions,
if that is the installation chosen.