Why do I get Invalid Argument just like that after 429 links

[LABELLEM2002]

Yes I figured that out right after I sent the message, I clicked the button
compact and repair and it went for 1.7 gig to 2.56 mb. Super thanks to you.
You helped me alot. I've changed it from OLE to Hyperlinks. The only thing is
that I get a warning message everytime I open the PDF but better that then
nothing I guess. I see that I can create a macro that would stop the
warnings, i'm trying this right now to see if it will help. If you have any
suggestions on this let me know. Youve been a super help.

 

[Dirk Goldgar]

Youve been a super help.

Oh, not me -- Klatuu.

 

[Paulo Salvador]

Dear friend,

I read your posts helping LABELLEM2002 in the discussion group.

You know, I have a similar case that I'd like you to help me.

My database, after filling more than 1600 records with ole objects, tex,
memo and id fields, started showing "invalid argument" each time I try to
insert one more Ole Object (bmp). My file has 1.99 GB. If I use the text
fields there's no problem and I can add more and more data. The problem is if
I put one OLE Object.

Is this any kind of size limit? How can I overcome this? So many days
working on this pictures database...

Tks a lot

 

[Dirk Goldgar]

Dear friend,

I read your posts helping LABELLEM2002 in the discussion group.

You know, I have a similar case that I'd like you to help me.

My database, after filling more than 1600 records with ole objects,
tex, memo and id fields, started showing "invalid argument" each time
I try to insert one more Ole Object (bmp). My file has 1.99 GB. If I
use the text fields there's no problem and I can add more and more
data. The problem is if I put one OLE Object.

Is this any kind of size limit? How can I overcome this? So many days
working on this pictures database...

Tks a lot

There is definitely a size limit, and you have hit it. No Jet (Access)
database can be larger than 2GB. Your database is so large because of
the OLE objects. Bitmap images tend to be quite large, and even if you
try to save space by storing them in a compressed format like JPG
instead, Access stores a bitmap version of the image for display
purposes. I gather this will be fixed in Access 2007, but for now your
best approach is not to store images in your database. Instead, store
them in external files, and just store the path to the image in the
database, in a text field. Then use an unbound image control to display
the image when you want. In the Current event of the form, you set the
image control's Picture property to the path to the image for the
current record.

Note, though, that this approach won't work if you want to display these
images on a continuous form. You can work around that by using an
unbound form with multiple image controls, but then you have to handle
all the data loading and paging yourself, with code.