 | |
A2K: Failure to compact smoothy worries me
comp.databases.ms-access comp.databases.ms-access
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
A2K: Failure to compact smoothy worries me -
01-20-2011
, 06:45 PM
#2
| |||
| |||
|
|
On my last decompile, compact, compile, compact routine the following happened. I compacted using the option in the Tools menu and got this message; "Cannot open database Z:\Dev Folder\db1.mdb'. It may not be a database that your application recognizes, or the file may be corrupt." I then open the code editor and compile. Finally I compact again. I'm left with a source file that seems small and quicker and, apparently, in perfect working order and an undeleted db1.mdb file. So I'm puzzled here. Has this worked? Should I be worried? Is this fixable? |
Looks like Microsoft hasn't addressed error #3049 two versions later
than A2K3. I posted a similar message a couple days ago with no
replies (and could not find any help on the internet).
-pw
#3
| |||
| |||
|
|
On Fri, 21 Jan 2011 00:45:39 -0000, "buckskin" buckskin (AT) mailinator (DOT) com> wrote: On my last decompile, compact, compile, compact routine the following happened. I compacted using the option in the Tools menu and got this message; "Cannot open database Z:\Dev Folder\db1.mdb'. It may not be a database that your application recognizes, or the file may be corrupt." I then open the code editor and compile. Finally I compact again. I'm left with a source file that seems small and quicker and, apparently, in perfect working order and an undeleted db1.mdb file. So I'm puzzled here. Has this worked? Should I be worried? Is this fixable? Looks like Microsoft hasn't addressed error #3049 two versions later than A2K3. I posted a similar message a couple days ago with no replies (and could not find any help on the internet). -pw |
about the hassle of doing that, setting up the new relationships etc.
#4
| |||
| |||
|
|
"PW" <emailaddyinsig (AT) ifIremember (DOT) com> wrote in message news:q42ij65hqlta0vkf5hmua33pdn4k3uoera (AT) 4ax (DOT) com... On Fri, 21 Jan 2011 00:45:39 -0000, "buckskin" buckskin (AT) mailinator (DOT) com> wrote: On my last decompile, compact, compile, compact routine the following happened. I compacted using the option in the Tools menu and got this message; "Cannot open database Z:\Dev Folder\db1.mdb'. It may not be a database that your application recognizes, or the file may be corrupt." I then open the code editor and compile. Finally I compact again. I'm left with a source file that seems small and quicker and, apparently, in perfect working order and an undeleted db1.mdb file. So I'm puzzled here. Has this worked? Should I be worried? Is this fixable? Looks like Microsoft hasn't addressed error #3049 two versions later than A2K3. I posted a similar message a couple days ago with no replies (and could not find any help on the internet). -pw Is a potential fix to export all objects to a new db? I've always worried about the hassle of doing that, setting up the new relationships etc. |
automatically. Only thing you may have to set up is VBA references, so make
sure you compile any code to check that the reference libraries are there.
Phil
#5
| |||
| |||
|
|
IMHO Best way to repair a corrupt Db. Relationships will be imported automatically. Only thing you may have to set up is VBA references, so make sure you compile any code to check that the reference libraries are there. Phil |
#6
| |||
| |||
|
|
"PW" <emailaddyinsig (AT) ifIremember (DOT) com> wrote in message news:q42ij65hqlta0vkf5hmua33pdn4k3uoera (AT) 4ax (DOT) com... On Fri, 21 Jan 2011 00:45:39 -0000, "buckskin" buckskin (AT) mailinator (DOT) com> wrote: On my last decompile, compact, compile, compact routine the following happened. I compacted using the option in the Tools menu and got this message; "Cannot open database Z:\Dev Folder\db1.mdb'. It may not be a database that your application recognizes, or the file may be corrupt." I then open the code editor and compile. Finally I compact again. I'm left with a source file that seems small and quicker and, apparently, in perfect working order and an undeleted db1.mdb file. So I'm puzzled here. Has this worked? Should I be worried? Is this fixable? Looks like Microsoft hasn't addressed error #3049 two versions later than A2K3. I posted a similar message a couple days ago with no replies (and could not find any help on the internet). -pw Is a potential fix to export all objects to a new db? I've always worried about the hassle of doing that, setting up the new relationships etc. |
We did that with our data. It did not get rid of the error - no
change whatsoever. Perhaps we should try to do the same with the code
database.
-paulw
#7
| |||
| |||
|
|
On my last decompile, compact, compile, compact routine the following happened. I compacted using the option in the Tools menu and got this message; "Cannot open database Z:\Dev Folder\db1.mdb'. It may not be a database that your application recognizes, or the file may be corrupt." I then open the code editor and compile. Finally I compact again. I'm left with a source file that seems small and quicker and, apparently, in perfect working order and an undeleted db1.mdb file. So I'm puzzled here. Has this worked? Should I be worried? Is this fixable? |
making an MDE from that.
Fingers and toes crossed.
-paulw
#8
| |||
| |||
|
|
IMHO Best way to repair a corrupt Db. Relationships will be imported automatically. |
That is it will be laid out as a grid. Real pain when you have more
relationships than can fit on the screen.
Use the sysrels utility at the following location to copy the table
relationships layout window
http://www.trigeminal.com/lang/1033/...p?ItemID=12#12
Or use Save Restore Modify Relationship Window at
http://www.lebans.com/saverelationshipview.htm
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
#9
| |||
| |||
|
|
On Fri, 21 Jan 2011 15:21:07 GMT, "Phil" <phil (AT) stantonfamily (DOT) co.uk wrote: IMHO Best way to repair a corrupt Db. Relationships will be imported automatically. The layout of the relationships window will not copy automatically. That is it will be laid out as a grid. Real pain when you have more relationships than can fit on the screen. Use the sysrels utility at the following location to copy the table relationships layout window http://www.trigeminal.com/lang/1033/...p?ItemID=12#12 Or use Save Restore Modify Relationship Window at http://www.lebans.com/saverelationshipview.htm |
import those relationships?
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.