Bonjour Patricia!
J’aime bien les petits problèmes. Voici, ci-dessous, la solution selon Larry chez Microsoft.
Le problème n’est pas avec Access, mais bien avec le logiciel Photo Editor. Puisqu’il n’est plus disponible avec Office 2003, il faut donc lier les photos à ton Internet Explorer, qui peut afficher toutes les photos dans tes champs OLE de Access.
1. Ouvrez un dossier dans windows explorer.
2. Dans le menu Outils/options / options dossier choisir le Internet Explorer pour les PHOTOS.
C’est tout. Bonne chance.
La nouvelle mode, afin d’éviter ce problème dans les prochaines bases de données, est d’enregistrer les photos dans un dossier et de placer l’adresse (path) de la photo dans la base de données dans un Tableau dans le formulaire ou dans l’état (exemples compliqués : http://accdevel.tripod.com). Ainsi le formulaire ou l’état va chercher la photo dans le dossier et non plus dans le champ OLE de la base de données.
Steve
-----------------------------------------------------------
The samples for "Access 2000" in the following reference work with Access 2003. The problem with using OLE Object Fields, and Bound or Unbound OLE Frames, is that you put yourself at the mercy of whatever software the user has registered for the image file type. If you are getting a "fuzzy image," it's not Access' problem. "Photo Editor" was simply a COM-enabled image processing software package included with Office Pro 2000, that was installed, and by default, registered for many image file types. Any other COM-enabled image processing software package can be used... but may not give the results you'd like.
If you are not happy with the quality, and you can reset the registrations, use a folder window, Tools Options Folder Options, and register your browser . . . most browsers do a creditable job of rendering common image file types.
The sample imaging databases at http://accdevel.tripod.com illustrate three approaches to handling images in Access, and the download includes an article discussing considerations in choosing an approach. Two of the approaches do not use OLE Objects and, thus, avoid the database bloat, and some other problems, associated with images in OLE Objects.
If you are printing the images in reports, to avoid memory leakage, you should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm. PrintFailure.zip is an Access97 MDB containing a report that fails during the Access formatting process prior to being spooled to the Printer Driver. This MDB also contains code showing how to convert the contents of the Image control to a Bitmap file prior to printing. This helps alleviate the "Out of Memory" error that can popup when printing image intensive reports.
Larry Linson Microsoft Access MVP
