Small database grows to 2GB!

[Thooom]

Hi. A friend has a small database. The database consists of one table (only 70-80 records)...NO other objects. One or two of the fields in that table are of the Hyperlink type. Anyway, through normal use, this small database file has grown to 2GB! Obviously, it was never compacted, but still, 2GB is an extreme. After compacting, it was 100-200k. But quickly grew to 14-15MB again.

It's an ACC2002 database, running on ACC2002. Again, nothing unusual, other than the Hyperlink field type. No OLE objects, no graphics stored in the table, etc. I'm having trouble researching the Hyperlink field type in depth, and I think that may have something to do with it. If all else fails I'll create a new file and import the table. But I'd like to figure out why it's doing this. Does anyone have some ideas on how a small database can grow so huge? Thanks.


Thooom

 

[The_Doc_Man]

Though there is a hyperlink, does it point to something that is actually stored (embedded) in the db file? If so, does the embedded object change a lot? Have you virus-scanned the machine in question?

 

[Thooom]

Though there is a hyperlink, does it point to something that is actually stored (embedded) in the db file? If so, does the embedded object change a lot? Have you virus-scanned the machine in question?

No, the hyperlinks point to files on the local network's shares. What puzzles me when looking at the underlying data in the hyperlink field values is how Access "finds" the file being linked to...when the underlying data sometimes starts with this text:

"..\..\blahblahfolder\blahfolder\blah.doc".

It's missing the start of the vital UNC path (or mapped drive letter): "\\server\share\blahblahfolder\blahfolder\blah.doc" or "X:\blahblahfolder\blahfolder\blah.doc".

How does Access know where the actual file is, if it stores the address starts with something like: "..\..\"?

Yipe...if it CAN'T find the file, does it store the file's data somewhere in binary format?? Ouch!



Thooom