Access 2000 does not show edits made in 97
- Thread starter MaryC
- Start date
- Local time
- Today, 15:07
- Joined
- Feb 19, 2002
- Messages
- 47,849
Are you talking about data changes or object changes? Are you sure they are looking at the same database?
Object changes
yes, they are looking at the same database- it happens on every 97 database with 2000 users - sometimes a restart on the Access 2000 machine will help - sometimes no - the only fix so far is a rename and path change of the database to fake Access out into thinking it is a new datbase and for Access 2000 to recognize the object changes.
yes, they are looking at the same database- it happens on every 97 database with 2000 users - sometimes a restart on the Access 2000 machine will help - sometimes no - the only fix so far is a rename and path change of the database to fake Access out into thinking it is a new datbase and for Access 2000 to recognize the object changes.
Vassago
Former Staff Turned AWF Retiree
- Local time
- Today, 15:07
- Joined
- Dec 26, 2002
- Messages
- 4,748
They are probably not seeing the changes because Access 2000 has to convert the database when it opens it. This actually makes it a different database then the one the Access 97 users are using. They make changes to the Access 97 database, but these changes don't show up in the Access 2000 database. Then the Access 2000 users restart Access and reconvert the database, this is why they see the changes on restarting. Is that understandable? Why do you have users using both versions of Access? This generally is not a good idea because of the major differences between Access 97 and Access 2000.
No they are not converting they are opening
No they are not converting - they are opening the databases. They are not able to edit objects but are able to use and edit data. We have over 500 machines. The cost would be prohibitive to the company to change all to Office 2000. All the databases are programmed in 97 then used by both, which works fine except for updates not taking effect. This is both a network problem and field office - stand alone problem. If I have them email me the database and I change it and email it back they do not see object edits and yes they are seeing the same database because it is sent to them as an executable file which extracts to the original location and overwrites the old file. On the more complex databases in place I have both versions programmed, making everyting I do must be duplicated, but would like to know if there is a fix.
No they are not converting - they are opening the databases. They are not able to edit objects but are able to use and edit data. We have over 500 machines. The cost would be prohibitive to the company to change all to Office 2000. All the databases are programmed in 97 then used by both, which works fine except for updates not taking effect. This is both a network problem and field office - stand alone problem. If I have them email me the database and I change it and email it back they do not see object edits and yes they are seeing the same database because it is sent to them as an executable file which extracts to the original location and overwrites the old file. On the more complex databases in place I have both versions programmed, making everyting I do must be duplicated, but would like to know if there is a fix.
- Local time
- Today, 15:07
- Joined
- Feb 19, 2002
- Messages
- 47,849
You should NEVER modify objects in a database that your users have open for data entry. This is the road to corruption. Get EVERYONE to close the db and then replace the network copy. Then they can re-open the db and everyone will see the changes.
If the users have their own local copy of the front end an easy way of forcing them to download a new copy is:
1. create a table that contains two fields - version and a date/time field.
2. copy the table and give it the same name followed by _local.
3. put the first table in the be db and the second table in the fe.
4. When the db opens, run a query that compares the timestamps from the two tables. If they are identical, the db opens normally. If they are different, tell the user to download a new copy of the fe and close the fe so they can't use it.
5. Whenever you make a change to the fe, make sure you change the local and linked table timestamps.
If the users have their own local copy of the front end an easy way of forcing them to download a new copy is:
1. create a table that contains two fields - version and a date/time field.
2. copy the table and give it the same name followed by _local.
3. put the first table in the be db and the second table in the fe.
4. When the db opens, run a query that compares the timestamps from the two tables. If they are identical, the db opens normally. If they are different, tell the user to download a new copy of the fe and close the fe so they can't use it.
5. Whenever you make a change to the fe, make sure you change the local and linked table timestamps.
Databases are closed
It is not a user problem it is an Access problem - you should try it. make a simple form in 97 open it in 2000 don't convert - just open. then close the database. change the form in 97 then close the database and open it in 2000. the form will not be changed in 2000, but open it in 97 and it is changed. It might change if the computer is restarted, otherwise you must rename the file and change the path and Access 2000 will recognize the change.
It is not a user problem it is an Access problem - you should try it. make a simple form in 97 open it in 2000 don't convert - just open. then close the database. change the form in 97 then close the database and open it in 2000. the form will not be changed in 2000, but open it in 97 and it is changed. It might change if the computer is restarted, otherwise you must rename the file and change the path and Access 2000 will recognize the change.
Databases are closed (2)
It is not a user problem it is an Access problem - you should try it. Make a simple database and form in 97 close the database, then open it in 2000 don't convert - just open. Then close the database. Change the form in 97 then close the database and open it in 2000. The form will not be changed in 2000, but open it in 97 and the changes are there. It might change if the computer is restarted, otherwise you must rename the file and change the path and Access 2000 will recognize the change.
It is not a user problem it is an Access problem - you should try it. Make a simple database and form in 97 close the database, then open it in 2000 don't convert - just open. Then close the database. Change the form in 97 then close the database and open it in 2000. The form will not be changed in 2000, but open it in 97 and the changes are there. It might change if the computer is restarted, otherwise you must rename the file and change the path and Access 2000 will recognize the change.
- Local time
- Today, 15:07
- Joined
- Feb 19, 2002
- Messages
- 47,849
I don't have a problem. Make absolutely certain that everyone closes the db before you reopen it including A97.
When I edit a database it is not on anyone's computer but my own.
The database is not available to other users when I edit them. I edit it on my computer then copy it back to it's location - the network or emailed to field offices. That way I don't have to worry about someone trying to access it. They get notified it is down, then notified when it up and running. If they send it to me - they get it back as a self-extracter. I know you don't have a problem - Access 97 to Access 2000 does. I am not a newby and your remarks imply such. Obviously you have not run into this problem before. That is why I suggested you try it, if you have available both versions of Access. If you don't then you will not be able to duplicate the problem.
The database is not available to other users when I edit them. I edit it on my computer then copy it back to it's location - the network or emailed to field offices. That way I don't have to worry about someone trying to access it. They get notified it is down, then notified when it up and running. If they send it to me - they get it back as a self-extracter. I know you don't have a problem - Access 97 to Access 2000 does. I am not a newby and your remarks imply such. Obviously you have not run into this problem before. That is why I suggested you try it, if you have available both versions of Access. If you don't then you will not be able to duplicate the problem.
- Local time
- Today, 15:07
- Joined
- Feb 19, 2002
- Messages
- 47,849
You are new here and so don't know me. I don't make filp remarks. If I say I don't have the problem, it is because I KNOW I don't have the problem. I did try it. Exactly as you described. I opened an A97 db with A2k and closed it. I opened the same db with A97 and modified it and I added a new control to a form (you didn't say what kind of changes are being lost). I closed A97. I opened the db with A2K again and the new field was there. Then I did the whole thing again to make sure.
Access copies objects into memory when a db is opened. What you are experiencing sounds like a db that is using an object in memory rather than obtaining it fresh from the modified db. Could this be a server issue? Does it have the db in cache memory and is failing to refresh the cache when the db is modified?
Access copies objects into memory when a db is opened. What you are experiencing sounds like a db that is using an object in memory rather than obtaining it fresh from the modified db. Could this be a server issue? Does it have the db in cache memory and is failing to refresh the cache when the db is modified?
Access 2000 in Windows 20000
I am sorry - you did not explain that you tried it. The changes are any kind - from modifying a form as you did, to modifying a report. What is your operating system? The only common factor I have with the problem is that all the Office 2000 users are also on a Windows 2000 Pro. operating system. The Office 97 users are on Windows 98 machines. The problem is on stand alone machines as well as network - so it is not a network problem. I am wondering if it is an operating system cache problem - I thought Access 2000 was caching the info somewhere, which if it were the operating system, would explain why restarting the computer would fix the problem sometimes. I do appreciate your help - I have been fighting this problem for a year. Because I have so many different types of databases and the 2 versions, it has been a major headache, but now it is becoming a problem more than a headache. I finally had to do some in depth research - this is the only site that seemd to have some intelligent responses.
I am sorry - you did not explain that you tried it. The changes are any kind - from modifying a form as you did, to modifying a report. What is your operating system? The only common factor I have with the problem is that all the Office 2000 users are also on a Windows 2000 Pro. operating system. The Office 97 users are on Windows 98 machines. The problem is on stand alone machines as well as network - so it is not a network problem. I am wondering if it is an operating system cache problem - I thought Access 2000 was caching the info somewhere, which if it were the operating system, would explain why restarting the computer would fix the problem sometimes. I do appreciate your help - I have been fighting this problem for a year. Because I have so many different types of databases and the 2 versions, it has been a major headache, but now it is becoming a problem more than a headache. I finally had to do some in depth research - this is the only site that seemd to have some intelligent responses.
- Local time
- Today, 15:07
- Joined
- Feb 19, 2002
- Messages
- 47,849
I don't know what to tell you. I tried on another computer that has only AXP installed and used sneaker net to transfer the files. It did not have a problem seeing the changes.
Can you reliably reproduce the problem when the .mdb is stored locally rather than on a network drive?
Can you reliably reproduce the problem when the .mdb is stored locally rather than on a network drive?
Stand Alone machine
Yes - I have machines in the field offices that I have updated and the cahnges were not seen until they did a restart or go through the process of renaming I described earlier. I actuall amde some changes in my motel room, put it on a floppy, transferred it on a field computer and had to go through all the rigamaro to get it to see the changes. I made the assumption of it being an Access problem. I think it is a Windows 2000 problem. I tried it last night on an XP machine and immediately could see the changes. I was going to try Windows 98 with Access 2000 today. I am sure I will find the same result as the XP. Thanks for your help.
I try not to make assumptions about people, but have learned as probably you have to doubt what some are doing. I always ask when they can't send email, "Did you dial the internet?" because they may not have done it.
I had a user call me just last Friday - with a print problem. They were on a time crunch to get the invoices out to the client. They said the green power light was off on the printer. Before they called me, they reloaded the printer software and drivers but to no avail - they could not print. I was just there the week previously and installed a mini network with internet sharing and this new printer. The power situation there was not real stable - even protected- being a construction site at a refinery in West Texas. I had them take the printer off the network and hook it directly to the computer - no help. Finally an hour later of loading - reloading - restarting -frustrated I said to have the mgr. call me ( thinking the printer was defective). 20 min later the mgr called me. I new he had the printer loaded on his laptop. Told him to hook the printer to it and try to print. He said he got an error message - I asked what it was- he said, Out of Paper. GRRRRRRR - I was hot. I had him load some paper in it and hook it back to the router and it was back in operation on the network. Then - this is the kicker - he asked, "So, what do you think was wrong with the printer?"
Yes - I have machines in the field offices that I have updated and the cahnges were not seen until they did a restart or go through the process of renaming I described earlier. I actuall amde some changes in my motel room, put it on a floppy, transferred it on a field computer and had to go through all the rigamaro to get it to see the changes. I made the assumption of it being an Access problem. I think it is a Windows 2000 problem. I tried it last night on an XP machine and immediately could see the changes. I was going to try Windows 98 with Access 2000 today. I am sure I will find the same result as the XP. Thanks for your help.
I try not to make assumptions about people, but have learned as probably you have to doubt what some are doing. I always ask when they can't send email, "Did you dial the internet?" because they may not have done it.
I had a user call me just last Friday - with a print problem. They were on a time crunch to get the invoices out to the client. They said the green power light was off on the printer. Before they called me, they reloaded the printer software and drivers but to no avail - they could not print. I was just there the week previously and installed a mini network with internet sharing and this new printer. The power situation there was not real stable - even protected- being a construction site at a refinery in West Texas. I had them take the printer off the network and hook it directly to the computer - no help. Finally an hour later of loading - reloading - restarting -frustrated I said to have the mgr. call me ( thinking the printer was defective). 20 min later the mgr called me. I new he had the printer loaded on his laptop. Told him to hook the printer to it and try to print. He said he got an error message - I asked what it was- he said, Out of Paper. GRRRRRRR - I was hot. I had him load some paper in it and hook it back to the router and it was back in operation on the network. Then - this is the kicker - he asked, "So, what do you think was wrong with the printer?"
- Local time
- Today, 15:07
- Joined
- Feb 19, 2002
- Messages
- 47,849
I recently ran into a very strange problem with an A2K database running on a Win2K network. You'd think Bill's children would play better together. I worked out when the problem happened although never why. So, I gave them a procedure to use to avoid the problem. Believe it or not, the problem never occured on my office PC, which was configured identically to all the users, because since I'm a developer, Access was always in my most recently used files list. Go figure.
