Stupid Nondescript Runtime Errors

[Dilo]

Using Microsoft software is like fighting with a grizzly bear As an
example:

I have a client's database which has the back end/front end structure
(programming and forms etc in the front end and data tables linked from the
back end) which gets round the stupid problem Access has of having a
different folder on my client's computer than on mine by relinking the tables
when it starts up. I have recently upgraded from Office XP Developer to
Office 2007 (after Vista SP2 broke Office XP for good) and the VBA code
compiles and runs in 2007 without error.

This is what I have been through in the last 2 days...

1. Needed a runtime version of the database so I used the Developer Add-In
to produce a package and installed it on an XP-SP3 computer getting a
nondescript runtime error when it started (relinking the tables).

2. Converted the database files to 2007, compiled, ran the database and
checked it was OK then repackaged - same runtime error when relinking.

3. Moved the database to my C: drive and placed it in a fixed folder,
relinked to the fixed back end and removed the relinking code. Repackaged -
NEW nondescript runtime error later in the database trying to use a form.

Quite frankly PATHETIC. I can't count the number of hours of my life I've
wasted just fighting with Access (and Windows and...). "Your potential, our
destruction of your potential" would be a better catchphrase!

Does anyone know how to get a runtime version to work without these useless
errors?

 

[Tom van Stiphout]

On Tue, 16 Jun 2009 19:00:01 -0700, Dilo

Can you quote the stupid non-descript error VERBATIM? Precise language
helps us help you. I understand you are upset, but we need this
information to help. My guess? You have a References problem and
forgot to write robust code at startup time to check for missing
references.

-Tom.
Microsoft Access MVP

 

[Gina Whipp]

Dilo.

Ummm, going to need to see those non-descript errors. I also noticed in all
the things you tried, placing the files in the Trusted Location was not
mentioned. You might also have a reference problem but those error messages
would really help!

--
Gina Whipp

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

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

 

[Tony Toews [MVP]]

I have a client's database which has the back end/front end structure
(programming and forms etc in the front end and data tables linked from the
back end) which gets round the stupid problem Access has of having a
different folder on my client's computer than on mine by relinking the tables
when it starts up.

And this is different than how other apps work how?

Office 2007 (after Vista SP2 broke Office XP for good)

How did Vista SP2 break Office XP?

1. Needed a runtime version of the database so I used the Developer Add-In
to produce a package and installed it on an XP-SP3 computer getting a
nondescript runtime error when it started (relinking the tables).

Do you have error handling in *all* your VBA code?

Tony