If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
access 2003 can't open an access 2000 mdb
Hello all,
I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean |
#2
|
|||
|
|||
access 2003 can't open an access 2000 mdb
What errors do you get when you open the A2000 mdb with A2003?
Permissions? References? Compile errors? Complaints about 'ActiveX'? If none of the above apply, the database is probably partially corrupt. A partially corrupt database may not be detected in its own version, but typically fails under another version, and a Decompile typically fixes this kind of issue. For suggestions on how to avoid corruption, see: Preventing Corruption at: http://members.iinet.net.au/~allenbrowne/ser-25.html -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message ... Hello all, I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean |
#3
|
|||
|
|||
access 2003 can't open an access 2000 mdb
If I remember correctly, it says the database is corrupt
and offers to repair it. The repair option does not work. Can you explain the Decompile in more detail? Sean -----Original Message----- What errors do you get when you open the A2000 mdb with A2003? Permissions? References? Compile errors? Complaints about 'ActiveX'? If none of the above apply, the database is probably partially corrupt. A partially corrupt database may not be detected in its own version, but typically fails under another version, and a Decompile typically fixes this kind of issue. For suggestions on how to avoid corruption, see: Preventing Corruption at: http://members.iinet.net.au/~allenbrowne/ser-25.html -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message ... Hello all, I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean . |
#4
|
|||
|
|||
access 2003 can't open an access 2000 mdb
Close Access.
Enter something like this at the command prompt. It is all one line, and include the quotes: "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb" Then uncheck the Name AutoCorrect boxes under: Tools | Options | General and compact the database: Tools | Database Utilities | Compact If that still fails, the next step would be to rebuild the database. This is really very quick. Just follow the 6 steps under the first symptom in this article: http://members.iinet.net.au/~allenbrowne/ser-47.html -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message ... If I remember correctly, it says the database is corrupt and offers to repair it. The repair option does not work. Can you explain the Decompile in more detail? Sean -----Original Message----- What errors do you get when you open the A2000 mdb with A2003? Permissions? References? Compile errors? Complaints about 'ActiveX'? If none of the above apply, the database is probably partially corrupt. A partially corrupt database may not be detected in its own version, but typically fails under another version, and a Decompile typically fixes this kind of issue. For suggestions on how to avoid corruption, see: Preventing Corruption at: http://members.iinet.net.au/~allenbrowne/ser-25.html "Sean" wrote in message ... Hello all, I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean |
#5
|
|||
|
|||
access 2003 can't open an access 2000 mdb
Well I tried the decompile. Got an access violation error
in Access. I'll the rebuild next. Thanks. Sean -----Original Message----- Close Access. Enter something like this at the command prompt. It is all one line, and include the quotes: "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb" Then uncheck the Name AutoCorrect boxes under: Tools | Options | General and compact the database: Tools | Database Utilities | Compact If that still fails, the next step would be to rebuild the database. This is really very quick. Just follow the 6 steps under the first symptom in this article: http://members.iinet.net.au/~allenbrowne/ser-47.html -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message ... If I remember correctly, it says the database is corrupt and offers to repair it. The repair option does not work. Can you explain the Decompile in more detail? Sean -----Original Message----- What errors do you get when you open the A2000 mdb with A2003? Permissions? References? Compile errors? Complaints about 'ActiveX'? If none of the above apply, the database is probably partially corrupt. A partially corrupt database may not be detected in its own version, but typically fails under another version, and a Decompile typically fixes this kind of issue. For suggestions on how to avoid corruption, see: Preventing Corruption at: http://members.iinet.net.au/~allenbrowne/ser-25.html "Sean" wrote in message .. . Hello all, I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean . |
#6
|
|||
|
|||
access 2003 can't open an access 2000 mdb
Ok,
Here's an interesting one. I was able to create a blank access 2000 database and import all my stuff into it. Access 2003 can open this one fine. Just for the heck of it, I tried to "decompile" this brand new db. I still get an "access violation" error message. Anyone know what's up w/ that? Sean -----Original Message----- Well I tried the decompile. Got an access violation error in Access. I'll the rebuild next. Thanks. Sean -----Original Message----- Close Access. Enter something like this at the command prompt. It is all one line, and include the quotes: "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb" Then uncheck the Name AutoCorrect boxes under: Tools | Options | General and compact the database: Tools | Database Utilities | Compact If that still fails, the next step would be to rebuild the database. This is really very quick. Just follow the 6 steps under the first symptom in this article: http://members.iinet.net.au/~allenbrowne/ser-47.html -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message ... If I remember correctly, it says the database is corrupt and offers to repair it. The repair option does not work. Can you explain the Decompile in more detail? Sean -----Original Message----- What errors do you get when you open the A2000 mdb with A2003? Permissions? References? Compile errors? Complaints about 'ActiveX'? If none of the above apply, the database is probably partially corrupt. A partially corrupt database may not be detected in its own version, but typically fails under another version, and a Decompile typically fixes this kind of issue. For suggestions on how to avoid corruption, see: Preventing Corruption at: http://members.iinet.net.au/~allenbrowne/ser- 25.html "Sean" wrote in message . .. Hello all, I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean . . |
#7
|
|||
|
|||
access 2003 can't open an access 2000 mdb
Close Access, and see if it leaves an ldb file in the folder where your
database is stored. If so, delete it. The ldb contains locking information - who has what locked. Access deletes the file when it closes, but after a crash the file can be left there with spurious locking info. Other than that, the only obvious idea is to check your service packs. You should have SP3 for Access 2000, and SP8 for JET 4. Both available from http://support.microsoft.com. -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message ... Ok, Here's an interesting one. I was able to create a blank access 2000 database and import all my stuff into it. Access 2003 can open this one fine. Just for the heck of it, I tried to "decompile" this brand new db. I still get an "access violation" error message. Anyone know what's up w/ that? Sean -----Original Message----- Well I tried the decompile. Got an access violation error in Access. I'll the rebuild next. Thanks. Sean -----Original Message----- Close Access. Enter something like this at the command prompt. It is all one line, and include the quotes: "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb" Then uncheck the Name AutoCorrect boxes under: Tools | Options | General and compact the database: Tools | Database Utilities | Compact If that still fails, the next step would be to rebuild the database. This is really very quick. Just follow the 6 steps under the first symptom in this article: http://members.iinet.net.au/~allenbrowne/ser-47.html -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Sean" wrote in message .. . If I remember correctly, it says the database is corrupt and offers to repair it. The repair option does not work. Can you explain the Decompile in more detail? Sean -----Original Message----- What errors do you get when you open the A2000 mdb with A2003? Permissions? References? Compile errors? Complaints about 'ActiveX'? If none of the above apply, the database is probably partially corrupt. A partially corrupt database may not be detected in its own version, but typically fails under another version, and a Decompile typically fixes this kind of issue. For suggestions on how to avoid corruption, see: Preventing Corruption at: http://members.iinet.net.au/~allenbrowne/ser- 25.html "Sean" wrote in message .. . Hello all, I've got an interesting problem here. I do my devel on an Access 2000 system. I make an mde file and distribute to me users (Access 2003), no real problems. If we try to open the Access 2000 mdb file with Access 2003, we get errors. It says it will try to repair the file, but it is never able to open it. If we try to run the Access 2003 convert tool, the same thing happens. Does anyone have any suggestions? Thanks Sean |
#8
|
|||
|
|||
NECESITAS DINERO EXTRA LEA ESTE ARTICULO????
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Installing Access 2000 with Office 2003 already installed | Jeremy | Setup, Installing & Configuration | 1 | July 14th, 2004 01:28 AM |
Access 2000 and Office 2003 | PJS | Setup, Installing & Configuration | 1 | June 7th, 2004 03:16 PM |
Access 2000 compatible with Office 2003 sbe | Ron | General Discussion | 2 | June 6th, 2004 04:31 AM |
Access 2003 less functional than Access 97? | George Hester | General Discussion | 2 | June 4th, 2004 04:53 PM |
Office 2003 and Office 2000/97 coexist on same PC? | John | General Discussions | 3 | May 6th, 2004 12:36 PM |