Search results

I know my judges can't be independent because I'm one of the AccessImagine developers. But if you like Ammara DBPix, it will be usefull to look at http://access.bukrek.net to compare.

There is an innovation in Access 2007 - regular Image control can be bound to a field/query with a picture path and filename. It works in continuous forms too. I know my judges can't be independent because I'm one of the AccessImagine developers. But if you like Ammara DBPix, it will be...

SOS, you are too fast... We could see some interesting postings here /gg

Hawn't you created a copy of database file as I guided you?

You can use a launching .bat file for front-end distribution @copy \\server\lala\database.adp "%TEMP%" /y >nul @start %TEMP%\database.adp There is one downside - front-end gets overwritten every time user opens it.

First of all, create a copy of your database file. In Access 2007, press big orb in top left corner, then Access Options. Take a look at Current Database category - there are a bunch of options you'd like.

You can try AccessImagine addon, it handles external storage (even with relative path to database) without any programming - so Flash drive wount be a problem. The bad news is it works only with images - but not with other document types :-(

Yep, my fault. IMAGE really works. Doesn't it bloat computer resources when displaying a table with lot of big images?

Hm, i havn't got the whole plot. There is several control types and several problems :-) Bound Object Frame - need an OLE object written to database, works with continuous forms. [Problem - OLE object size = uncompressed bitmap size] Attachment - writes files to database, works with continuous...

Its hard to write external image storage usually. You'll find some problems again and again. Beside that, its usually not easy for users to manipulate images in such a database. There is a ActiveX control called AccessImagine, which handles external image storage automatically and makes adding...

The problem is Access doesn't create separate controls for each record - or it would hang trying to display really big table. There is no straight workaround for this. The only way to do this is to generate small previews for each picture and store them in DB as OLE bitmaps. Then you display em...