|
 |
access thread: Copying problems
Message #1 by "Tim Smith" <tim.smith@g...> on Mon, 23 Dec 2002 16:07:45
|
|
I am in the middle of a situation with MS Access and I would like to post
the following scenario to all in the hopes that someone can help me.
To start, I have been working on an Access 97 application (using Windows
NT Workstation 4.0 SP 6). When I have modified any database object
(reports, forms, macros, etc). I have been copying the modified object to
a test version of the MDB on a server. I have done this by opening both
versions of the MDB file in separate windows, and using drag-and-drop to
update the objects in the server version of the database.
As luck would have it, the server crashed during one of the update
sessions.
Since then, I have not been able to perform the drag-and-drop copy. When
I attempt to do so, I get two error messages:
1) Record(s) can't be read; no read permission on MSysModules (3112)
2) Object is invalid or no longer set (3420)
When I exit from Access (the window that contains the source database), I
get an application error dialog that reads:
The instruction at "0x65160912" referenced memory "0x0000002a". The memory
could not be "read".
Both my machine and the server have been rebooted, but the problem still
exists. When I go to another computer (also NT 4.0 SP 6) and try the drag-
and-drop, the same error messages occur. When I try to copy the object to
a newly created database on my computer, I also get the error messages.
The problem does not occur when I access other MDB's on the same server,
which makes me believe that the server crash during the drang-and-drop
copy somehow corrupted both of the MDBs (the one on my machine and the one
on the server).
Thanks
Tim Smith
Sr. Application Developer
Golf Digest Companies/Advance Magazine
Trumbull CT
Message #2 by "Hamilton. Tom" <hamiltont@s...> on Mon, 23 Dec 2002 08:07:49 -0800
|
|
Hi Tim,
You should try 'Repairing' the databases using(from within Access)
[Tools], [Database Utilities], [Repair Database]
-----Original Message-----
From: Tim Smith [mailto:tim.smith@g...]
Sent: Monday, December 23, 2002 8:08 AM
To: Access
Subject: [access] Copying problems
I am in the middle of a situation with MS Access and I would like to
post
the following scenario to all in the hopes that someone can help me.
To start, I have been working on an Access 97 application (using Windows
NT Workstation 4.0 SP 6). When I have modified any database object
(reports, forms, macros, etc). I have been copying the modified object
to
a test version of the MDB on a server. I have done this by opening both
versions of the MDB file in separate windows, and using drag-and-drop to
update the objects in the server version of the database.
As luck would have it, the server crashed during one of the update
sessions.
Since then, I have not been able to perform the drag-and-drop copy.
When
I attempt to do so, I get two error messages:
1) Record(s) can't be read; no read permission on MSysModules (3112)
2) Object is invalid or no longer set (3420)
When I exit from Access (the window that contains the source database),
I
get an application error dialog that reads:
The instruction at "0x65160912" referenced memory "0x0000002a". The
memory
could not be "read".
Both my machine and the server have been rebooted, but the problem still
exists. When I go to another computer (also NT 4.0 SP 6) and try the
drag-
and-drop, the same error messages occur. When I try to copy the object
to
a newly created database on my computer, I also get the error messages.
The problem does not occur when I access other MDB's on the same server,
which makes me believe that the server crash during the drang-and-drop
copy somehow corrupted both of the MDBs (the one on my machine and the
one
on the server).
Thanks
Tim Smith
Sr. Application Developer
Golf Digest Companies/Advance Magazine
Trumbull CT
Message #3 by Tim.Smith@g... on Mon, 23 Dec 2002 12:17:01 -0500
|
|
Tom -
Thanks for answering this post so quickly.
I have runt he Repair Utility on both the source and destination MDB files
- to no avail.
I am still trying to resolve this, though.
Thanks
Tim
"Hamilton. Tom"
<hamiltont@s... To: "Access" <access@p...>
nty.net> cc:
Subject: [access] RE: Copying problems
12/23/02 11:07 AM
Please respond to
"Access"
Hi Tim,
You should try 'Repairing' the databases using(from within Access)
[Tools], [Database Utilities], [Repair Database]
-----Original Message-----
From: Tim Smith [mailto:tim.smith@g...]
Sent: Monday, December 23, 2002 8:08 AM
To: Access
Subject: [access] Copying problems
I am in the middle of a situation with MS Access and I would like to post
the following scenario to all in the hopes that someone can help me.
To start, I have been working on an Access 97 application (using Windows
NT Workstation 4.0 SP 6). When I have modified any database object
(reports, forms, macros, etc). I have been copying the modified object to
a test version of the MDB on a server. I have done this by opening both
versions of the MDB file in separate windows, and using drag-and-drop to
update the objects in the server version of the database.
As luck would have it, the server crashed during one of the update
sessions.
Since then, I have not been able to perform the drag-and-drop copy. When
I attempt to do so, I get two error messages:
1) Record(s) can't be read; no read permission on MSysModules (3112)
2) Object is invalid or no longer set (3420)
When I exit from Access (the window that contains the source database), I
get an application error dialog that reads:
The instruction at "0x65160912" referenced memory "0x0000002a". The memory
could not be "read".
Both my machine and the server have been rebooted, but the problem still
exists. When I go to another computer (also NT 4.0 SP 6) and try the drag-
and-drop, the same error messages occur. When I try to copy the object to
a newly created database on my computer, I also get the error messages.
The problem does not occur when I access other MDB's on the same server,
which makes me believe that the server crash during the drang-and-drop
copy somehow corrupted both of the MDBs (the one on my machine and the one
on the server).
Thanks
Tim Smith
Sr. Application Developer
Golf Digest Companies/Advance Magazine
Trumbull CT
Message #4 by jbird@a... on Mon, 23 Dec 2002 12:11:54 -0500
|
|
Tim,
Did you try making copies of the files and working with the copies? Or creating
all new files and copying over all the objects? I know that may be cumbersome
but that has worked for in the past when a mdb file become corrupted.
Tim.Smith@g... on 12/23/2002 12:17:01 PM
Please respond to "Access" <access@p...>
To: "Access" <access@p...>
cc: (bcc: Joe Bird/ACS)
Subject: [access] RE: Copying problems
Tom -
Thanks for answering this post so quickly.
I have runt he Repair Utility on both the source and destination MDB files
- to no avail.
I am still trying to resolve this, though.
Thanks
Tim
"Hamilton. Tom"
<hamiltont@s... To: "Access"
<access@p...>
nty.net> cc:
Subject: [access] RE: Copying
problems
12/23/02 11:07 AM
Please respond to
"Access"
Hi Tim,
You should try 'Repairing' the databases using(from within Access)
[Tools], [Database Utilities], [Repair Database]
-----Original Message-----
From: Tim Smith [mailto:tim.smith@g...]
Sent: Monday, December 23, 2002 8:08 AM
To: Access
Subject: [access] Copying problems
I am in the middle of a situation with MS Access and I would like to post
the following scenario to all in the hopes that someone can help me.
To start, I have been working on an Access 97 application (using Windows
NT Workstation 4.0 SP 6). When I have modified any database object
(reports, forms, macros, etc). I have been copying the modified object to
a test version of the MDB on a server. I have done this by opening both
versions of the MDB file in separate windows, and using drag-and-drop to
update the objects in the server version of the database.
As luck would have it, the server crashed during one of the update
sessions.
Since then, I have not been able to perform the drag-and-drop copy. When
I attempt to do so, I get two error messages:
1) Record(s) can't be read; no read permission on MSysModules (3112)
2) Object is invalid or no longer set (3420)
When I exit from Access (the window that contains the source database), I
get an application error dialog that reads:
The instruction at "0x65160912" referenced memory "0x0000002a". The memory
could not be "read".
Both my machine and the server have been rebooted, but the problem still
exists. When I go to another computer (also NT 4.0 SP 6) and try the drag-
and-drop, the same error messages occur. When I try to copy the object to
a newly created database on my computer, I also get the error messages.
The problem does not occur when I access other MDB's on the same server,
which makes me believe that the server crash during the drang-and-drop
copy somehow corrupted both of the MDBs (the one on my machine and the one
on the server).
Thanks
Tim Smith
Sr. Application Developer
Golf Digest Companies/Advance Magazine
Trumbull CT
Message #5 by "Hamilton. Tom" <hamiltont@s...> on Mon, 23 Dec 2002 09:46:30 -0800
|
|
Another thought - I have run into problems with secured databases (those
using work group *.mdw files) - I have repaired/compacted those files
and gained relief. The only catch is you may need a clean copy of the
MDW to log in with before you can correct the corrupt/confused copy.
I would start by trying to repair your mdw file. If you haven't
specified a custom one, then Access defaults to the SYSTEM.MDW in your
Windows, or WINNT\System folder.
To find out which you can use this line for the DEBUG (immediate) window
? SysCmd(acSysCmdGetWorkgroupFile)
Use Access to Repair (if A97) or Repair/Compact (if A2k/AXP)
-----Original Message-----
From: Tim.Smith@g... [mailto:Tim.Smith@g...]
Sent: Monday, December 23, 2002 9:17 AM
To: Access
Subject: [access] RE: Copying problems
Tom -
Thanks for answering this post so quickly.
I have runt he Repair Utility on both the source and destination MDB
files
- to no avail.
I am still trying to resolve this, though.
Thanks
Tim
"Hamilton. Tom"
<hamiltont@s... To: "Access"
<access@p...>
nty.net> cc:
Subject: [access] RE:
Copying problems
12/23/02 11:07 AM
Please respond to
"Access"
Hi Tim,
You should try 'Repairing' the databases using(from within Access)
[Tools], [Database Utilities], [Repair Database]
-----Original Message-----
From: Tim Smith [mailto:tim.smith@g...]
Sent: Monday, December 23, 2002 8:08 AM
To: Access
Subject: [access] Copying problems
I am in the middle of a situation with MS Access and I would like to
post
the following scenario to all in the hopes that someone can help me.
To start, I have been working on an Access 97 application (using Windows
NT Workstation 4.0 SP 6). When I have modified any database object
(reports, forms, macros, etc). I have been copying the modified object
to
a test version of the MDB on a server. I have done this by opening both
versions of the MDB file in separate windows, and using drag-and-drop to
update the objects in the server version of the database.
As luck would have it, the server crashed during one of the update
sessions.
Since then, I have not been able to perform the drag-and-drop copy.
When
I attempt to do so, I get two error messages:
1) Record(s) can't be read; no read permission on MSysModules (3112)
2) Object is invalid or no longer set (3420)
When I exit from Access (the window that contains the source database),
I
get an application error dialog that reads:
The instruction at "0x65160912" referenced memory "0x0000002a". The
memory
could not be "read".
Both my machine and the server have been rebooted, but the problem still
exists. When I go to another computer (also NT 4.0 SP 6) and try the
drag-
and-drop, the same error messages occur. When I try to copy the object
to
a newly created database on my computer, I also get the error messages.
The problem does not occur when I access other MDB's on the same server,
which makes me believe that the server crash during the drang-and-drop
copy somehow corrupted both of the MDBs (the one on my machine and the
one
on the server).
Thanks
Tim Smith
Sr. Application Developer
Golf Digest Companies/Advance Magazine
Trumbull CT
Message #6 by "Tim Smith" <tim.smith@g...> on Mon, 23 Dec 2002 18:53:53
|
|
I found a way around the situation I described earlier today. This did
not fix the MDB files, but I was able to use the drag-and-drop copy method
to update the server version of the MDB file.
First, I created a new, empty MDB file (using the standard MS Access File
| New)
Second, I opened the source MDB, and for each object I needed to copy
(fortunately, the development process was at a point where I needed to
update less than 10 items), I used the File | Export function to export
the object the newly created MDB file.
I then used the newly created MDB file as the source file and was able to
successfully drag-and-drop copy the objects to the server version of the
file.
I plan on writing a small VBA routine to mimic this for all objects in the
Query, Form and Report collections. I will post that later.
Thanks
Tim
|
|
|
View Cart
