Errors encountered running Access 2003 under Vista

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm in the midst of a database project for a client: Big contract, so I
splurged
and bought a new machine, running Vista Business. I've installed both Office
2003 Pro and Office 2007 Pro. It seems to take the two versions fine,
however, whenever I attempt to write ANY code in Access 03 the system blows
up.
Error message: "Access has encountered a problem and is closing". Nothing
else to help me know what the problem is. Near as I can deduce it has
something to do with VBA running under Vista.

I copied the database back to the old sluggard (running XP Pro and Office 03)
and I can actually get work done. The VB Editor doesn't blow up, code works
fine, even functions like Count() work on my form & report controls. In the
Vista environment they return NAME# errors.

Any ideas &/or suggestions? What am I missing that won't enable me to run
Access 03 in Vista?

I'm about ready to send MS a nasty email telling them where they can put
Vista, but perhaps I'm the optimist and not wanting to give up the newer =
better yet.
 
Check your VBA references. Sounds like a reference version issue because of
the two versions installed.
 
I'd assume that you're stuck with some crap database that still uses DAO

DAO isn't available on Vista

rewrite it as ADO
 
Aaron Kempf said:
I'd assume that you're stuck with some
crap database that still uses DAO

DAO isn't available on Vista
Click to expand...

That is simply not true. What "kicks" do you get out of spreading
misinformation, Mr. Kempf?

Larry Linson
Microsoft Access MVP
 
What is wrong with you?
DAO is supported in 2007 if you use 2003 format (mdb)
In addition, the OP said he was trying to develop in 2003

Do you think you are funny or is it you just don't know?

--
Dave Hargis, Microsoft Access MVP


Aaron Kempf said:
I'd assume that you're stuck with some crap database that still uses DAO

DAO isn't available on Vista

rewrite it as ADO
Click to expand...
 
What is wrong with you?
DAO is supported in 2007 if you use 2003 format (mdb)
In addition, the OP said he was trying to develop in 2003

Do you think you are funny or is it you just don't know?
Click to expand...


Sounds like References in the VBE window. This might be tricky to set
if it blows up when you open the VBE. If this is the case, you'll
have to import objects and code into a new .mdb, making sure you also
set up needed properties (like AppIcon), and references. If your VBA
code is lazy and doesn't include explicit references to DAO or ADO
(Dim rs as DAO.Recordset) then the order of references is important.
You should use explicit references.

Duane
 
What is wrong with you?
DAO is supported in 2007 if you use 2003 format (mdb)
In addition, the OP said he was trying to develop in 2003

Do you think you are funny or is it you just don't know?
Click to expand...


Sounds like References in the VBE window. This might be tricky to set
if it blows up when you open the VBE. If this is the case, you'll
have to import objects and code into a new .mdb, making sure you also
set up needed properties (like AppIcon), and references. If your VBA
code is lazy and doesn't include explicit references to DAO or ADO
(Dim rs as DAO.Recordset) then the order of references is important.
You should use explicit references.

Duane
 
I think that you're full of crap and anyone using DAO for anything
should be fired and then spit upon
 
DAO is called WHAT in vista again?
DAO is called WHAT in vista again?
DAO is called WHAT in vista again?


DAO is called WHAT in Office 2007 again?
DAO is called WHAT in Office 2007 again?
DAO is called WHAT in Office 2007 again?
 
Back
Top