ACCESS closes unexpectedly

[Miles]

Have a (4MB without data) ACCESS 2000 format database with
records containing thumbnail images and other data.
Thumbnail is refreshed each time a user navigates records
(via normal record navigation cursor).

In testing db in my View Data form, if I repeatedly and
quickly click the record navigation (seemingly faster than
ACCESS can refresh the thumbnail), after about 5 or so
clicks, ACCESS unexpectedly closes leaving the .ldb file
apparently open in Explorer. The database file can
immediately be reopened without any problems.

Am changing design so user can toggle whether or not to
show thumbnails. However problem will remain if
thumbnails are visible; it doesn't seem catastrophic but
is clearly undesirable. Any explanations or suggestions
as to resolving it? TIA

 

[cTaHk0]

Have a (4MB without data) ACCESS 2000 format database with
records containing thumbnail images and other data.
Thumbnail is refreshed each time a user navigates records
(via normal record navigation cursor).

In testing db in my View Data form, if I repeatedly and
quickly click the record navigation (seemingly faster than
ACCESS can refresh the thumbnail), after about 5 or so
clicks, ACCESS unexpectedly closes leaving the .ldb file
apparently open in Explorer. The database file can
immediately be reopened without any problems.

Am changing design so user can toggle whether or not to
show thumbnails. However problem will remain if
thumbnails are visible; it doesn't seem catastrophic but
is clearly undesirable. Any explanations or suggestions
as to resolving it? TIA

Hi, try using different method, I suggest you this way:
Put your pictures in one folder (c:\pictures) or any other, then in your
table where pictures are stored insert one text field witch contains names
of each picture you need, with full path example (C:\pictures\picture1.jpg)
named this field fldPicture or something.

fldPicture

C:\pictures\picture1.jpg

C:\pictures\picture2.jpg

C:\pictures\picture3.jpg

 

[Exponent]

Common suggestions to workaround this are:

Suppress/Lock the navigation buttons to prevent the user scrolling ‘too quickly’.

Don’t display the image in this view – require the user to switch to a different view to trigger loading
the image.

You’ll find more info on these at The Access Web:
http://www.mvps.org/access/toc.htm

Finally, you could consider using a third-party image control, such as our own, which works fully asynchronously.

 

[Guest]

Thanks; will try it!

-----Original Message-----



Hi, try using different method, I suggest you this way:
Put your pictures in one folder (c:\pictures) or any other, then in your
table where pictures are stored insert one text field witch contains names
of each picture you need, with full path example (C:\pictures\picture1.jpg)
named this field fldPicture or something.

fldPicture

C:\pictures\picture1.jpg

C:\pictures\picture2.jpg

C:\pictures\picture3.jpg

.


In form where you need to see pictures create one image box with name
"ImageBox" or something and for picture properties use none (leave it
empty). Put also field from table "fldPicture" in this sample, and in form
events - On Current add this simple code:

Me.ImageBox.Picture = Me.FldPicture

And then see your hard work result )

I hope I help you

Regards,

CtaHk0


.

 

[Guest]

Thanks; will look at the site and ponder.

-----Original Message-----


Common suggestions to workaround this are:

Suppress/Lock the navigation buttons to prevent the user scrolling 'too quickly'.

Don't display the image in this view - require the user

to switch to a different view to trigger loading

the image.

You'll find more info on these at The Access Web:
http://www.mvps.org/access/toc.htm

Finally, you could consider using a third-party image

control, such as our own, which works fully asynchronously.