A
Anthony Wieser
I have a database that I made a small edit to on my Vista machine
running access 2007.
The database is on a network shared drive (not ntfs).
The query still opens fine on access 2007, but on my XP machine running
office 2000, when I open or try to edit the query, Access 2000 just closes
with no error message at all. There is also no entry made in the
application event log.
When I attach my debugger, Visual Studio reports an unhandled exception at
0x1b018900 in MSACCESS.EXE
Access violation writing 0x00040ffc
The debug window in the debugger also lists:
First-chance exception at 0x3008753c (Stack Overflow)
First-chance exception at 0x30087552 (Access violation reading location
0x00040fb0)
First-chance exception at 0x1b018900 (Access violation writing location
0x00040ffc)
followed by the unhanlded exception listed below.
So, clearly the file's not working somehow.
So, two questions:
* Has anyone else seen this happen?
* Does anyone know how to repair the database.
Queries I haven't modified in 2007 still work, but any that have been saved
are broken.
The tables still appear to work.
Does anyone at Microsoft know anything about this, as there's nothing listed
in the knowledge bases that I've found so far.
Anthony Wieser
Wieser Software Ltd
running access 2007.
The database is on a network shared drive (not ntfs).
The query still opens fine on access 2007, but on my XP machine running
office 2000, when I open or try to edit the query, Access 2000 just closes
with no error message at all. There is also no entry made in the
application event log.
When I attach my debugger, Visual Studio reports an unhandled exception at
0x1b018900 in MSACCESS.EXE
Access violation writing 0x00040ffc
The debug window in the debugger also lists:
First-chance exception at 0x3008753c (Stack Overflow)
First-chance exception at 0x30087552 (Access violation reading location
0x00040fb0)
First-chance exception at 0x1b018900 (Access violation writing location
0x00040ffc)
followed by the unhanlded exception listed below.
So, clearly the file's not working somehow.
So, two questions:
* Has anyone else seen this happen?
* Does anyone know how to repair the database.
Queries I haven't modified in 2007 still work, but any that have been saved
are broken.
The tables still appear to work.
Does anyone at Microsoft know anything about this, as there's nothing listed
in the knowledge bases that I've found so far.
Anthony Wieser
Wieser Software Ltd