New problem for Access???? Scott Burke 12/19/2008 2:50:11 PM 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

RE: New problem for Access???? Clifford Bass 12/20/2008 12:51:19 AM 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" wrote: [Quoted Text] > 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

RE: New problem for Access???? Scott Burke 12/22/2008 9:28:01 PM 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" wrote: [Quoted Text] > 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" wrote: > > > 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

RE: New problem for Access???? Clifford Bass 12/23/2008 1:26:00 AM 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" wrote: [Quoted Text] > 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

RE: New problem for Access???? Scott Burke 12/24/2008 5:29:01 PM 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 "Clifford Bass" wrote: [Quoted Text] > 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" wrote: > > > 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

Re: New problem for Access???? "ErezM via AccessMonster.com" <u45095[ at ]uwe> 12/24/2008 8:56:26 PM 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- [Quoted Text] >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 Scott Burke wrote: >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 -- May all beings be happy. Message posted via http://www.accessmonster.com

RE: New problem for Access???? "AccessVandal via AccessMonster.com" <u18947[ at ]uwe> 12/26/2008 6:36:42 AM 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. Scott Burke wrote: [Quoted Text] >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 -- Please Rate the posting if helps you Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200812/1

RE: New problem for Access???? "Clifford Bass via AccessMonster.com" <u48370[ at ]uwe> 12/27/2008 1:04:34 AM 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 wrote: [Quoted Text] >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 -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200812/1

Re: New problem for Access???? Scott Burke 12/31/2008 2:21:01 PM 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 "ErezM via AccessMonster.com" wrote: [Quoted Text] > 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 > > Scott Burke wrote: > >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 > > -- > May all beings be happy. > > Message posted via http://www.accessmonster.com > >