Search results

I have an Access 97 reporting DB. On all other systems these reports print out fine. I just set up this reporting system on a new computer and when I print, the reports print on two pages - second page had a tid bit of an order date. On the other systems, all the page margins ( top, bottom...

hmm ? I don't think that would work after the fact ( after entering the data ) ... default values are only applied to new records. I would suggest to run code to update all Null values to 0 before summing the info in the fields. You cannot calculate null fields. QT = )

Oooppss .... I mis-posted this message ... it should actually be in the "Reports" section ... how can I move the post. I want to refrain from creating a double post. Anyone ? QT :confused:

I have an Access 97 reporting DB. On all other systems these reports print out fine. I just set up this reporting system on a new computer and when I print, the reports print on two pages - second page had a tid bit of an order date. On the other systems, all the page margins ( top, bottom...

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...

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 = (

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...

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...

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

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...

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...

AAAAAARRRRRRGGGGGGG!!!!! I HAVE COMPLETELY REMOVED 2003 using the MS Office 2003 Resource Kit >> Completely Uninstalled Office 97 using Office 97 Eraser tool >>> Ran Registry Mechanic >>> Reinstalled Office 97 >>>> AND NADA!!!! SAME ERROR !!!!! WHAT THE ... HECK! DID OFFICE 2003 install that...

OK, i FOUND THE O 2003 RESOURCE KIT ... THIS SHOULD DO THE TRICK ... QT :mad:

HOW THE !@#$%^ DO I COMPLETELY REMOVE ALL REMINANTS OF OFFICE 2003 ??????? GEEEEEEEZZZZZZ! I'M REALLY GETTIN' TICKED NOW! FOLDER IS STILL THERE WITH ALL KINDS OF .DLL's ... PLUS I HAVE NO IDEA WHAT OTHER FILES ARE ON THE SYSTEM THAT ARE BEING REFERENCED ....AHHHHHHHHHHH!!!! QT :mad:

Installed the Windows Install clean up utility and Office 2003 OR office 97 does not show up in the list !!!!!! QT :mad:

Hhmmm.... Alrighty .... In my references list, I have ( in order of Priority ): Visual Basic for Applications Microsoft Access 8.0 Object Library Microsoft DAO 3.5 Object Library I cannot move the priority on the DAO priority. When I run the update queries attempt to run, I get this error...

I read through quickly and it sounded to me like the same utility that is used when you choose to Add/Remove programs. This is what I have been using all along. Hmmm, ok, I have O97 cleanup tool and the Windows Installer CleanUp Utility. I going to try to re-create the problem before I start...

See, I think the issue if completely removing the OFFICE 2003 version. That's what I think may be causing the problem. Since none of these systems are accessible to me at the moment, I am going to recreate the issue on a local laptop. O97 is installed. I am going to install the database...

Gotcha ... I'll check the knowledgebase ... thxs. QT

Will try ... I don't have the reference list with me ( there were 4 in total ) ... but I know I have already tried to force the refresh on two of the references. The other two would not allow me to do so, stating the DB required them to run. .... Pat you are right .... I believe there was...