 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Setup / Configuration / May 2006upgrading DB from 97 to Access 2k
We have been running a backend Database using Access 97, Ihave been trying for sometime to get it upgraded to Access 2k. everytime I get it upgraded using the upgrade utility in Access 2k the DB will run for a day or two ok then the crazy thing goes bananas. It continually gives errors that this is not a recognized database format and so on. I repair and compact the database and it may or may not work correctly I usually wind up changing it back to 97. I have even created new tables using the same filed names and importing the data into the new tabkes with the same results. Can anyone give me an idea as to what may be happening? Thanks in advance for any assistance. jmillerwv my experience is that macros (and this includes those embedded in the buttons) can be lost in such an upgrade. you should methodically go thru each function of the application and test with test data. I would also monitor the data in the tables that you add with your test to see if it is stable. the fact that it is working ok for "a day or two" makes me think that there is a feature broken but it is not a feature used frequently.... unfortunately I can't be sure this will help - but I've seen flaky behavior due to this...  SignatureNTC > We have been running a backend Database using Access 97, Ihave been trying > for sometime to get it upgraded to Access 2k. everytime I get it upgraded [quoted text clipped - 7 lines] > > jmillerwv thanks for your assistance. the only real problem is the data. The front end has been in Access 2k for about 2 years or better. It is just when I move the data from Access 97 to Access 2k that the problem crops up. I will look at the front end again and see if I cna pinpoint the porblem. Again thanks for your assistance. jmillerwv > my experience is that macros (and this includes those embedded in the > buttons) can be lost in such an upgrade. [quoted text clipped - 22 lines] > > > > jmillerwv it may not be feasible......but I wonder if you open a new db and import both back-end & front-end - so you unsplit the db ; just to see if it is stable... if so; then split.... crude guess and probably too manually intensive - may be feasible experiment if small.... SignatureNTC > thanks for your assistance. the only real problem is the data. The front end > has been in Access 2k for about 2 years or better. It is just when I move the [quoted text clipped - 30 lines] > > > > > > jmillerwv Believe it or not but I have tried that ( combining the frontend and backend then splitting them in 2000) same results. I have not tried to run the DB in the unsplit fasshion but I will try that using an copy of it for test purposes and see how it goes. Again thanks for your assistance. If it goes crazy then I will repost. jmillerwv > it may not be feasible......but I wonder if you open a new db and import both > back-end & front-end - so you unsplit the db ; just to see if it is stable... [quoted text clipped - 38 lines] > > > > > > > > jmillerwv well you know trouble shooting is eliminating unknowns....and working with a single unsplit version on one pc eliminates alot of unknowns... in one upgrade 97-2k I lost alot of macros inexplicably....I had to hunt them down and re-enter.... SignatureNTC > Believe it or not but I have tried that ( combining the frontend and backend > then splitting them in 2000) same results. I have not tried to run the DB in [quoted text clipped - 46 lines] > > > > > > > > > > jmillerwv Again thank you for your assistance. I will make a dummy db using the current data and current frontend and try combining them and see what happens. I will post a new thread when I get the dummy db up and running to let you know how what I find out. This just happened the front end had a problem when it was shutting down and requested to send Microsoft the error. got an answer back MS says up grade to newest verision of Office to solve the problem. I don't even know what the probelm was. Just thought that was kind of funny, I guess upgrading always fixes the problem. Have a good day and weekend I will let you know how it goes. jmillerwv > well you know trouble shooting is eliminating unknowns....and working with a > single unsplit version on one pc eliminates alot of unknowns... [quoted text clipped - 52 lines] > > > > > > > > > > > > jmillerwv >We have been running a backend Database using Access 97, Ihave been trying >for sometime to get it upgraded to Access 2k. everytime I get it upgraded >using the upgrade utility in Access 2k the DB will run for a day or two ok >then the crazy thing goes bananas. It continually gives errors that this is >not a recognized database format and so on. This frequent corruption upon upgrading to A2000 can be caused by the Oplocks problem. However this hasn't been a problem for a year or two if the server and workstations OSs are up to the latest service pack level. I wonder if the A2000 are all at the most recent SP? And if the Jet 4.0 SP are all the same and reasonably current? What I've done is use the various API calls available and am checking the version number and date/time of a crucial dll, msjetxx.dll, to ensure it matches what I have on my system. See the Verify Appropriate Jet Service Pack is installed page at my website for more details including sample code: www.granite.ab.ca\access\verifyjetsp.htm What is the OS running on your server? Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony, Thanks for the reply. the os of the server is Small Business Server 2003 sp1 fully patched. Operating systems of the work stations is a mix of Windows XP Pro SP@ fully patched, and Windows 2000 Pro updated and patched. All OS's are kept updated weekly by myself. My phylosophy is " An updated and Patched OS is a happy OS." I will take a look at your suggestion on the jet verify and let you know. Again thanks for the reply. jmillerwv > >We have been running a backend Database using Access 97, Ihave been trying > >for sometime to get it upgraded to Access 2k. everytime I get it upgraded [quoted text clipped - 20 lines] > > Tony >Thanks for the reply. the os of the server is Small Business Server 2003 sp1 >fully patched. Operating systems of the work stations is a mix of Windows XP >Pro SP@ fully patched, and Windows 2000 Pro updated and patched. All OS's are >kept updated weekly by myself. My phylosophy is " An updated and Patched OS >is a happy OS." Ok, good. I just wanted to double check that you weren't on some real old OSs or running a four year old version of ****nix on the server. Tony SignatureTony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.