Serious Issue ...

If you have VBA... does "OnErrorResumeNext" help until you sort this out?
I would definetly check your results...! -Just a thought- :eek:
 
I DO NOT HAVE 2000+ installed any longer on this system. Everything has been wiped out by the MS Removal Wizard in the MS Office 2003 Resource Kit.

I reinstalled '97 ONLY! But it seems it may still be referencing something from 2003 ... WHY ? AND WHAT ? I don't know ....

As for Jet 4.0 .... I can not figure out how to check the version ... I do not have VB on this system and that is the app. that they suggest to run to check the version.

Would the JET version cause this type of issue ???

This SUCKS ! ahhhhgg!
 
Last edited:
Personally, I thought maybe the reason your query was now "not updatable" was because it was referencing the Jet 4.0 engine, although your reference selections and registry settings should be toward the Jet 3.5 engine for your app.

Would having Jet 4.0 cause something like this? Normally I don't believe so. Just eliminating probable causes, in one of the links, MS states Jet 4.0 handles Queries differently than in Jet 3.5. Originally I was thinking of deleting your Jet 4.0 dll's, but now I believe that may / would cause more problems than possibly solve.

Doc was asking you to recompile your code and then check. I was suggesting that if you were calling a Query etc. from code on a Form etc. to insert "OnErrorResumeNext" in the beginning of that statement... if compiling it didn't help. Usually putting in "OnErrorResumeNext" is NOT a good idea because it skips the immediate error and moves on.

Another thing Ghudson has said before is to 'uncheck' ALL of your references, click Apply/OK. And then later 'recheck' ALL of your correct references to force a refresh, see if that helps.

Maybe this will help:
How To Ensure Jet 3.5 Is Installed Correctly
Here
 
Windsailor ... thanks for the article ... I am going to go through it methodically and verify that everything is correct.

Yes, I have re-compiled the code and forced a refresh on the reference list. However, the top two references I am unable to uncheck ... 1) VB for Apps, 2) MS Access 8.0 Object Library. Get message box .. "Can't remove this reference. Signpro Sign Estima 2005 needs this reference to work properly."

Here ... I am attaching 1 of about 150 of the queries that crap out on the update.

PLS NOTE: This query will give you results on a system that has ONLY Office 97 installed .. and never had a 2000+ install. If at any one point Office 2000+ has been installed on the system ... you will expect to receive an error .. "Must use an updatable query". Easy fix .... change the Unique Records propery to 'No'. I need to know why it does not work when 2000+ is installed. Is it a reference issue? Hhhmmmm ...

Let me know ... any input at this point ... and throughout this painstaking debugging process is HIGHLY, HIGHLY appreciated.

Thanks in advance ....
QT :confused:
 

Attachments

I've just run this on a machine with access 97 and Office XP pro (including Access 2002) and it runs OK. I guess thats not what you expected to hear but I hope you find your answer soon.
 
I am wondering if you have an orphaned record in your data. MS access 97 was very good at "hiding problems" it seemed to run very well, until it suddenly decided that there was a problem it couldn't cope with and it would crash. So I am wondering if there is an orphaned record that MS Access 97 is ignoring, but when you update the system, it then recognizes the problem, and decides that it won't play anymore.
 
Just an FYI...
My system has 97, 2000, and 2002 installed
The query worked just fine for me.
 
This is ridiculuous! I actually recreated the problem on two seperate machines, and I no one else is getting the same error??

Now I am stumped!!!!

QT
 
References.

I know that reference have been mentioned but hpw about this 1.

Microsift DAO 2.5/3.51 Compatability Library.
This can be found in the following place (possibly)
C:\Program Files\Common Files\Microsoft Shared\DAO\DAO2535.TLB

I will also attach it if it is not there.

Also. I had this problem a while ago in Access 2000 and amended a query slightly. This then worked.
 

Attachments

Win XP - A2002 - ran fine.

One thing I will recommend - remove the : from the table and query names, and the spaces and # from the field names. If you want these names to appear as column headings enter the name in the "Caption" field in the properties at the bottom.

I have read countless posts reporting : and # causing all sorts of strange errors and results.

HTH

Dave
 
OLDSOFTBOSS: Naming conventions are only to name a few nonconventional items apparent in this DB. This DB was existent when I started here. I would create a mess if I went through and changed all the table names. There are about 300-400 update queries of the sort in this db. Renaming these tables is not an option.

I can not understand why no one else can reproduce the error. I had it occuring on 2 other systems ( 1 XP, and 1 '98 OS ) ... now I just reproduced it on another 2 XP boxes and my east coast rep. it is also happening to has an XP box ... but no one on this site and another forum I'm on is it happening to .... que passa ??

I am stumped! Can anyone reproduce the error ? ..... this doesn't make any sense!

QT = (
 
Last edited:
Inherated Db's are fun !!

Could it be a permissions thing with your network ?? Other than that, I have no idea.

Sorry
 
Take it back ... take it back ... those are lies!! hahah a! = )
Uhh no, not fun at all!

As for permissions, I am not securely familiar with XP security. The PC is on the network as part of the workgroup, not the domain.

All permissions for the folder that the test DB is in have full control access for 2 users and the admin.

Should there be something else in the way of permissions I should be looking at ?

QT = (
 
Will try ...

Ok, I'm on it .... I'll see if that works.

Get back to you in a bit ... Thanks!

Still haven't corrected the problem ... this is NOT a good sign!

QT = (
 
Fixed >> Solved >> Done >> Pronto !!!!

;) :) ;) :)
YES!! You saw CORRECTLY!! The problem is FIXED!!

Now that I think back, all, now 5, systems had fresh installs of Office 97.

THE FIX: Previous to this message, WindSailor suggested to update my version of Microsoft Jet. Now I'm not sure if this is what actually solved the problem, BUT along the way I had to have the SR-2b patch installed, in order to upgrade Jet. And THAT DID IT!

I just ran the SR-2B patch ... AND TTaaaa DDDaaaaaa !!

I want to thank EVERYONE very much for taking the time to read through the post, run the test UpdateError.mdb and for sending all the documentation my way. You guys are fantastic, really !

Many Thanks!
QT ;)
 
Last edited:
You must log in or register to reply here.

Similar threads

A
Solved Connection String mysterious Trim
Replies
3
Views
736
cheekybuddha
cheekybuddha
G
Updating from Access 2013 to 365?
Replies
15
Views
1,206
The_Doc_Man
The_Doc_Man
T
Back End Read-Only Issue
2
Replies
26
Views
2,031
Gasman
Gasman
S
Access Distribution Software To Replace Sagekey
Replies
2
Views
686
CJ_London
C
D
Remote desktop vs. browser based web apps.
Replies
14
Views
3,567
Albert D. Kallal
A

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top Bottom