Load Pix into a Large frame for viewing

[chlowden]

why compress the file? doe sthis affect the web publishing?

[Fenton]

No. This is a FileMaker operation. In 7 it now says: Save a Copy As, then "Compacted copy (smaller)". Sorry for the confusion. I never use it myself anymore, because I have FileMaker Developer 7, which has a special "File Maintenance" command, which does it to the current file without going through this 3 step procedure.

Saving as compacted goes through the file, removing any unused space, which you have a fair amount of after you delete a bunch of container objects. Filemaker does a fair job of this anyway, when you close the file. But the above does it better.

Then you throw away the original file and use the " Copy" one, after removing that extra suffix.

[be careful. Do not Save a Copy as " Clone," then throw away the original. Clone is a empty file.]

[Fenton]

No. This is a FileMaker operation. In 7 it now says: Save a Copy As, then "Compacted copy (smaller)". Sorry for the confusion. I never use it myself anymore, because I have FileMaker Developer 7, which has a special "File Maintenance" command, which does it to the current file without going through this 3 step procedure.

Saving as compacted goes through the file, removing any unused space, which you have a fair amount of after you delete a bunch of container objects. Filemaker does a fair job of this anyway, when you close the file. But the above does it better.

Then you throw away the original file and use the " Copy" one, after removing that extra suffix.

[be careful. Do not Save a Copy as " Clone," then throw away the original. Clone is a empty file.]

[Fenton]

No. This is a FileMaker operation. In 7 it now says: Save a Copy As, then "Compacted copy (smaller)". Sorry for the confusion. I never use it myself anymore, because I have FileMaker Developer 7, which has a special "File Maintenance" command, which does it to the current file without going through this 3 step procedure.

Saving as compacted goes through the file, removing any unused space, which you have a fair amount of after you delete a bunch of container objects. Filemaker does a fair job of this anyway, when you close the file. But the above does it better.

Then you throw away the original file and use the " Copy" one, after removing that extra suffix.

[be careful. Do not Save a Copy as " Clone," then throw away the original. Clone is a empty file.]

[chlowden]

Well, after some discovering ... it seems to works a treat. Thank you very much. I don't understand fully how it works but I am looking in to it.

Lastly, what is the "PhotoID" & "Ouverture" fields do & what do I link them to?

Thank you

[chlowden]

Well, after some discovering ... it seems to works a treat. Thank you very much. I don't understand fully how it works but I am looking in to it.

Lastly, what is the "PhotoID" & "Ouverture" fields do & what do I link them to?

Thank you

[chlowden]

Lastly, I find that it does not work on web publishing via the net. Is this normal?

[chlowden]

Lastly, I find that it does not work on web publishing via the net. Is this normal?

[chlowden]

Last of the lasts, my orginal file was 350megs. Now it is upto 450megs. Is there any reason?

Also, I do not understand the

"When you have, delete all the Photo fields in that table." instruction. I can't find where all the photo fields are in the table? Is this emprty info that when removed reduces the file size?

[chlowden]

Last of the lasts, my orginal file was 350megs. Now it is upto 450megs. Is there any reason?

Also, I do not understand the

"When you have, delete all the Photo fields in that table." instruction. I can't find where all the photo fields are in the table? Is this emprty info that when removed reduces the file size?

[Fenton]

PhotoID is the field we are setting with a script, in order to show the photo in the big frame.

"Ouverture", I have no idea. It's your field.

Originally you had the photos in the main table, in fields Photo1, Photo2, etc.. I said Import them into another table, into 1 field, Image.

After importing the original photos are still in the original table. If the imports were successful, you should be able to delete those fields (Photo1, Photo2, etc.). Be sure to have backups in case something goes wrong.

I added the "Save a Copy As, Compacted" procedure in order to slim the file down. It's optional. That may be the 450 to 350 difference; that is kind of a large gap, but I've seen large savings with that procedure.

I don't see why it wouldn't work with IWP on the web, as long as the images are embedded, but I haven't tried it.

[Fenton]

PhotoID is the field we are setting with a script, in order to show the photo in the big frame.

"Ouverture", I have no idea. It's your field.

Originally you had the photos in the main table, in fields Photo1, Photo2, etc.. I said Import them into another table, into 1 field, Image.

After importing the original photos are still in the original table. If the imports were successful, you should be able to delete those fields (Photo1, Photo2, etc.). Be sure to have backups in case something goes wrong.

I added the "Save a Copy As, Compacted" procedure in order to slim the file down. It's optional. That may be the 450 to 350 difference; that is kind of a large gap, but I've seen large savings with that procedure.

I don't see why it wouldn't work with IWP on the web, as long as the images are embedded, but I haven't tried it.

[chlowden]

Ok, I just took your DB and importted into the image field each of the 20 photo fields from the old one. I presume that it amounts to the same thing. I always say, if it ain't broke, don't fix it.

I will now try and really understand the logic of all this.

Thank you for your extreme generosity

[chlowden]

Ok, I just took your DB and importted into the image field each of the 20 photo fields from the old one. I presume that it amounts to the same thing. I always say, if it ain't broke, don't fix it.

I will now try and really understand the logic of all this.

Thank you for your extreme generosity