Does anyone know what this 'PropDataCopy' means & how to circumven

J

JC007

I'm creating a new .MDB file for the purpose of migrating all the objects of
another .MDB file into this new one.

I realized that the database (.MDB) file which I'm trying to migrate is
currently not corrupted but there's something wrong with the file. You see
if I try to 'zip' or 'compress' the file using the 'Winzip' utility instead
of the file decreasing in size it actually increases a few KB's. At first, I
found this kind of odd, and then I thought that it's possible that there's
something legitimately wrong with it. This may also explain why when this
database becomes corrupted it becomes unrepairable.

When I import all the objects to this newly created database (.MDB) and
check the approriate references in the VBA window, I'm able to compile, then
'Compact and Repair Database' and everything seems to be fine. However, when
I try to 'Compact and Repair' by calling the 'MsAcc.CompactRepair' function
using a Visual Basic application that I developed it places the following
string in the log (.LOG) file.

Modules Container: 'PropDataCopy' stream has a length of zero!


Attempted solutions:
* I tried to copy and paste the module and create each one separately, and
that didn't work.
* I also tried to copy and paste, but this time pasting it first into a text
editor 'TextPad' to get rid-off any possible unseen chars that may be a
problem.
* I tried loading the new access database using the /Decompile option and
see if that would help, but it didn't.
* I looked up the workd 'PropDataCopy' in the MSDN help and could not find
anything on it.

At this point I ran out of options and kind of my last hope is that someone
could shed some light into this matter in this newsgroup and let me know how
can I get rid-off this message when I 'Compact and Repair' the database via
VB->Access API.
Or Whether this is something not to worry about.

Background information:
* MsAcc is a native "Microsoft Access 10.0 Object Libray' object variable.
* Function Syntax:
MsAcc.CompactRepair(LogFile:=True, _
SourceFile:=strSource, _
DestinationFile:=strDestination)

JC007
Thanks.
Yours Trully.
 
J

Jerry Whittle

I've noticed this with WinZip before. Sometimes it just doesn't work well
with .MDB files or the smaller database files just don't have anything
compressable in them. In fact I just tried to compress 4 different databases
and it didn't do more that 3% no matter the compression setting such as Fast,
Normal, or Max. These databases were all around 1 MB in size. On the other
hand, I used Winzip on a 500 MB database file and it compressed it down to 38
MB.

I recommend trying JetComp to repair any problem database files.
 
J

JC007

I really thank you for your prompt response. I forgot to mention that after
migrating (importing) all the objects from the old to the new database, I was
able to compress that new database by 81% from its original size.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top