[piper]

And you did install Photo Editor from your Office CD? This Microsoft link states that you'll see "package" when Photo Editor isn't installed.

Try this:
1. uninstall Photo Editor
2. detect/repair on Access
3. reinstall Photo Editor

You could investigate one of the other options (using Visual Basic or converting files to BMP format).

Please post the results.

[Advertisements]

LindaGail:

I got it to work, well, mostly anyway.

When inserting the picture, I have to click "Microsoft Photo Editor 3.0 Picture" from the drop down list instead of "File". When Photo Editor opens, I just click "Open Picture" and select the one from my documents.

Now the photo is embedded in the database and shows up on my report.

That, however, is where I'm having my next problem. The picture shows up but is too large for the frame. I'm sure this is an easy fix. I'll just resize the field in Design View on the report.

What I'm realizing now, though, is that I'm not sure how many photos Security will have per document. For instance, let's look at these two scenarios:

1. Lady tripped on a rug, fell down, and hurt her hand. Security may take only a single photo of the lady's hand.

2. Two car pile up caused by our Valet Department. Security will probably take a photo from each of four sides from both vehicles for a total of eight photos.

Another scenerio may have even more photos!! Wow. I'll have to add about 20 OLE fields to the table to make sure they have enough space for documentation. I'm hoping now that when I enter these into the table and get them resized for the report that the report won't print out 5 or 6 blank pages for those reports that only have one or two photos in them. I'm hoping the report will disreguard the fields with null data to keep the report short.

At any rate, you've taken care of my problem. Now that I understand how the OLE works, I can see things clearly now. I think fixing the rest will just be simple trial and error.

Thanks for taking care of this for me. My security department will be glad you did.



Magus

Edited by magusbuckley, 11 January 2007 - 01:13 PM.

[magusbuckley]

LindaGail:

I got it to work, well, mostly anyway.

When inserting the picture, I have to click "Microsoft Photo Editor 3.0 Picture" from the drop down list instead of "File". When Photo Editor opens, I just click "Open Picture" and select the one from my documents.

Now the photo is embedded in the database and shows up on my report.

That, however, is where I'm having my next problem. The picture shows up but is too large for the frame. I'm sure this is an easy fix. I'll just resize the field in Design View on the report.

What I'm realizing now, though, is that I'm not sure how many photos Security will have per document. For instance, let's look at these two scenarios:

1. Lady tripped on a rug, fell down, and hurt her hand. Security may take only a single photo of the lady's hand.

2. Two car pile up caused by our Valet Department. Security will probably take a photo from each of four sides from both vehicles for a total of eight photos.

Another scenerio may have even more photos!! Wow. I'll have to add about 20 OLE fields to the table to make sure they have enough space for documentation. I'm hoping now that when I enter these into the table and get them resized for the report that the report won't print out 5 or 6 blank pages for those reports that only have one or two photos in them. I'm hoping the report will disreguard the fields with null data to keep the report short.

At any rate, you've taken care of my problem. Now that I understand how the OLE works, I can see things clearly now. I think fixing the rest will just be simple trial and error.

Thanks for taking care of this for me. My security department will be glad you did.



Magus

Edited by magusbuckley, 11 January 2007 - 01:13 PM.

[magusbuckley]

LindaGail:

In reguards to your post #16. I'm sure you'll see "Package" if Microsoft Photo Editor isn't installed correctly, but mine was. The reason I was getting this, so you'll know in the future, is because when I clicked OLE object and it asked me what type, I was given two choices. The first was a drop down list of the different programs installed on the computer, the second was "From File". I checked "From File". Therefore, Access had the file, it just didn't know what program to use for opening it. After clicking "Microsoft Photo Editor 3.0" from the drop down list, everything was OK.

Magus

[piper]

Not a problem...

Picture in the report
Open the report in Design Mode
Right click the photo field
Choose Properties
All tab - Size Mode (3rd down)
Change to Stretch

Multiple photos
It sounds like you need a database of possible claims, that will include photos. I suggest two tables, linked. The main table for the pertinent facts of the claim, the second table only to hold photos. Each photo record will be linked back to the main table (a one-to-many relationship).

This is fairly simple to accomplish. Let me get some stuff together on it, and I'll get back to you. If my synopsis of that database isn't accurate, please explain.

[piper]

I've uploaded a small database for your review. It has two tables: Main and Supporting. The Supporting table links back to the Main table. There are two Forms (Table1 is the Main form and Table2 is the Sub-form - open Table1), and a Report.

You can download the zipped database here: http://www7.spread-i...64649ce384583db

Let me know if that's close to what you need to accomplish.

[piper]

MagusBuckley, this database was created with Access 2003. If you have issues opening it, let me know. I've got Access 2002 at home and it won't take any time to recreate in that version.

[magusbuckley]

LindaGail:

I'm downloading your sample database now. I have several important projects to take of at work so may not be able to work on this today. If I don't find time, I'll take it home and look at it over the weekend.

If the report will skip fields with null data, I think I'll be all set. I'll post back with more information later. Your synopsis is correct.

Thanks,

Magus

[piper]

Skip fields with null data... If there's nothing in the field, it will appear blank in the report. Do you want to skip the entire record if one or more fields are blank? I don't know what exactly you're shooting at, so I can answer it. I am sure we can figure out how to do what you want to do, it'll just take more communication.

Couple of hints to throw out regarding this:
Set up a query to show only records where field1, field 2, and field3 are not null
Set up a query where date is in range
Base the report on the query instead of the table

If you have Crystal Reports, we could whip up a tremendous report

[magusbuckley]

LindaGail:

We do not have Crystal Reports.

Skipping Null Data - Clarification: I'll try to explain this a little better. In the table, I'm going to give Security 20 fields for storing photos (whew...hopefully that's enough). On the report, I'll have it print all fields from the table. So the first part of the report will print fields containing record number, type of incident, date of occurance, measures taken to resolve the problem, etc. Following that, of course will be the photos.

Now pretend we're dealing with my example one from a previous post where a lady falls down and hurts her hand. Security only took a single photo of that incident. When they print the report, it will be going through a query so they will only be printing that one incident. The report prints out...will it have attempted to print the reamining fields for the other 19 photos security never took? If so, they'll have the incident followed by several blank pages of empty fields. If the report will over look the fields without photos, the report would print only up to the one and only photo taken. That's what we're shooting for here.

I downloaded and played with your sample database. The relation you have between the two tables seems to take care of this problem, though I'm not sure how you set up the relation. Until now, I had planned on putting all the documentation in the same table with the photos. Now I see this may not be the way to go. I'll look at your sample some more during the day when I find some free time. I'm pretty sure I'll be able to figure out how you set that up.

When trying to insert a large photo, I'm still getting the memory error. I may have to have them resize the photos before imputting them into the database. They probably won't like that idea because they'll want the highest resolution possible so they can get the best photos for documentation. I was trying to insert a 4 MB photo into the database and got the following error:



I had a few programs running, but this is a new computer with plenty of RAM. Memory shouldn't be an issue right now. I've received the same message with the same sized photos while running only Access. Not sure yet what's causing this. If I can get it to work, I'm wondering if memory will become an issue a few months down the road after Security has importated about a hundred photos are so into the database. With photos at around 4 megs eache, that's a really big database.

Oh, and I used your "Stretch" option. It worked. That's another hurdle out of the way.

With all this work, I think I could have just sent you the layout and paid you to set this up for us. If probably would have been quicker. Still, I love learning.

Thanks for your help thus far.

Magus

[piper]

I'll look into the memory error and get back to you.

To understand the linking, open both tables in Design View and see the fields I've used. Then go to the Tools menu, Relationships and see how I linked them together.

I agree - learning is fun

[piper]

Well, corection to my prior post. I didn't put the tables in Relationships (but I should have). So when you go to Relationships, right click to Add Tables, choose both tables. When they pop in you'll see a line with an arrow from Main to Supporting. You can click the relationship line between the tables, right click and Edit Relationship to see more information. This is how Access knows that for every one record in Main, there may be more than record (or no records) in Supporting - it's a one-to-many relationship.

For more information on linking tables, Access has some good information in the Help file. Key in 'link tables' and look for a topic called About Relationships in an Access Database.

Let me know if you have any other questions.

[magusbuckley]

LindaGail:

I think I can take it from here. Boy, we've been through a lot. Thanks for all your help.

If I ever find time to finish this project, I'll let you know what the Security Group.

Magus

[Konraad]

Hello:

At work, our security officers fill out reports on incidents that happen on property. From time to time, they take digital photos. For now, they key the data into a protected worksheet in Excel. They insert the pictures into a word document and print it all out. They have come to realize that it is too difficult to find old incident reports and match them with the photos. To solve the problem, I'm thinking of creating an Access Database to house all of the information, including the photos. So far, though, I'm thinking I'm out of luck. I can't find a way to put photos into a database.

Do any of you know if this is possible, and if so, how would I go about doing it?

Any and all information will be greatly appreciated.

Thanks,

Magus

Hi,
In my opinion the best solution is to use Excel and hyperlinks to the photos. In that case photos could be large and the Excel file would be still quite small. To open the file someone could just click on the hyperlink. After that external program would open (in my case it was IE).
This solution needs to have some network space to store all files in one place. It is quite easy to put correct link to the file into the cell.

Does it help you?

Cheers,
Konraad