New problem for Access????

[Scott Burke]

I not sure if this is the site for this problem. If you know a better site
please suggest it. Thank you

I have an Access 2003 program ( ISSORDERENTRY.MDB ).
Last week it worked fine. This week it has a problem. ????

The Problem:
Access will not handle .DBF files any more!
The ISSORDERENTRY.MDB gets it's price list via a DBF(4) file.
When the program tries to open the file it does one of the two below.
1) Nothing. It does not error and does not open, link, or anything else.
2) You get this error :
The Mircosoft Jet Database engine could not find the object 'MAGNINFO.DBF'.
Make sure the object exists and that you spell its name and the path name
correctly.

Yes! The name and path are correct.
Excel can open MAGINFO.DBF with no problems.
The problem shows up on two XP Pro's and one Vista.
The programs worked last week. This week there are errors.
The program ISSORDERENTRY.MDB has NOT been changed in over 6 months.
Interesting note:
The fourth computer can run ISSORDERENTY.MDB without errors or problems.
This computer has NOT been turned on in over two weeks!

Does anyone know if the last Microsoft update might have cause .DBF problems?
How would I find out if it did?
Has anyone else have / heard of this problem?

I have searched the internet and have found nothing.
Maybe I have not used the right word in my search.
Right now I am in the dark. All ideals will be tried.

Thank you for your time.
Scott Burke

 

[Clifford Bass]

Hi Scott,

It sure sounds like an update from Microsoft caused the problem. You
could try rolling back the most recent updates, see if that helps.

Clifford Bass

 

[Scott Burke]

Hi Clifford,
Thank you for the idea. I know how to roll backup a single
driver but How do you roll back a lot of them?

Scott Burke

 

[Clifford Bass]

Hi Scott,

This is for Windows XP; other versions may vary somewhat. Go to
Control Panel, Add or Remove Programs. At the top there is a "Show updates"
check box. Check that. Look for updates from Microsoft that were installed
after the date on which the program last worked correctly. Click on each and
click on the Remove button. Note that you will have to check the updates
under several Microsoft programs. Unfortunately, not all list the install
date. There is probably a log file somewhere that details what was installed
and when. Where I do not know. A post in the appropriate Windows newsgroup
might get you some help there.

Hope that helps,

Clifford Bass

 

[Scott Burke]

Hi Cllifford,
I tried that. I even went back two weeks. Still did not fix
the problem. I am going to look for that log. Maybe it is one of those
things that once it is installed it can't be uninstalled.

Thanks for your time Cillford.
Have fun tomarrow.

Scott Burke

 

[ErezM via AccessMonster.com]

hi
i sometimes run into situations where a working mdb is no longer working.
in all those cases, it has moved between computers.
what is going on behind the scenes is: if computer 1 ran the mdb properly,
but has, say access 2002 (or word 2002 or excel 2002, if they are referenced
in the code), and then the mdb is ran by a newer version (a computer with
excel or word or anything!! newer in terms of versions), then access
automatically upgrades the references.
and that's when the problem starts, cause the older coputer cannot downgrade
the references back, and breaks in the most unusual places (not really
related to the missing reference)

after all that is said, open the VBE code window (Alt-F11), and in tools-

references, see if something has "Missing" in front of it, if it has, remove

the check box and scroll down to find the replacement reference

good luck
Erez

 

[AccessVandal via AccessMonster.com]

Hi Scott,

Can you share some input regarding the windows update?
Here’s list of my updates that are likely causing me problems
KB956803
KB956841
KB954211
KB957095
KB956391
KB958644
KB954459
KB957097
KB955069

Running on WinXP and A2K as well as WinXP with Access 2007 Runtime.

I have checked all these updates info. Two was the nearest or likely culprit
KB956391 and KB954459.

KB954459 affect A2K3.

 

[Clifford Bass via AccessMonster.com]

Hi Scott,

Thanks! I did and trust you did too!

I have probably hit my limit on things to try that are not drastic.
Hopefully someone else will have an idea for you.

Clifford Bass

 

[Scott Burke]

B-I-N-G-O!!!!!!!!!
Hi ErezM
You win the 2 cent award! The admeration of all who are in
this group and my personal thank you. Thank you!

I did not think to check the references because there was no
error that pointed to them. Live and learn.


Again Thank you
Scott Burke

 

[AccessVandal via AccessMonster.com]

Thanks for posting back.

ErezM, it never occur to me that newer referances can cause problems. I need
to check further on this although mine has nothing to do with referances.

B-I-N-G-O!!!!!!!!!
Hi ErezM
You win the 2 cent award! The admeration of all who are in
this group and my personal thank you. Thank you!

I did not think to check the references because there was no
error that pointed to them. Live and learn.

Again Thank you
Scott Burke

hi
i sometimes run into situations where a working mdb is no longer working.

[quoted text clipped - 50 lines]