Corrupted database iPhoto 6.0.6

My main iPhoto library resides on an external HDD. I have several other smaller iPhoto libraries on the iMac and I use Brian Webster's iPhoto Library Manager v3.2.4 to switch between them. Also, I occasionally access my main iPhoto library over the wireless network from my daughter's MacBook, again using iPhoto Library Manager. This has all worked fine until now. Last evening we launched it from the MacBook. Today when I launched from the iMac there are about 1500 photographs missing according to iPhoto. Apparently I have no photos more recent than April 2006. The originals and modified versions are all there but iPhoto doesn't see them. I was prompted to rebuild the thumbnail cache when I launched and I did....I think it had already decided the photos were missing.
Any help in restoring things to their previous state will be much appreciated. I really don't relish the thought of reimporting, adjusting and relabelling so many pictures.

The fading memory has, I think, remembered the real story about the v7 update. It was nothing to do with Software Update trying to distribute it. I think I downloaded it on her MacBook because I thought we should be running v7 already if Apple had just released iLife '08. So easily confused!! When it failed to install I trashed it.
I've been researching further, particularly on Brian Webster's iPLM site, and reckon the corruption is to do with permissions. Some file's and folders have my wife's permissions and some have mine. Before moving the library to the HDD it used to be in the shared users' public folder and we both accessed it via aliases in our own Pictures folders. I showed my wife how to download and import pictures from her camera (from her user area) last Sunday. This was the first time she had done it and probably was when the problem occurred.
My March library seems to be working fine so I suppose I will just have to reimport the more recent pictures to it. Any suggestions about how best to do this? I'm thinking I'll just have to bring in the Originals and then redo any modifications.

Similar Messages

  • ? Corrupted Library6.iPhoto file?

    I updated iPhoto to 7.1.2 a few days ago. On opening iPhoto the next AM I noticed that all my pictures from summer 2006 to present are missing when running iPhoto; those before summer 2006 remain. It was a few days since I had looked at pictures before the upgrade. Fortunately, all my pictures appear to be in the correct place and are viewable with Preview when I click on the photo file (user/Pictures/iPhoto Library/) on the internal hard drive. Whew!
    I've reviewed the forum for the last 2 hours and assume that I have a corrupted database file. Not sure if it is the Library6.iPhoto file or albumData.xml file. I have tried copying both of these from my SuperSuper backup volume (done last Sunday evening automatically before I knew I had a problem) on my external hard drive without correction of the problem. Should I also try to copy over the Library.iPhoto file? I didn't see this recommended elsewhere.
    Prior posts recommended copying over the Library6.iPhoto file if a backup was available, and if no improvement, to rebuild the library using iPhoto Library Manager. Before jumping into this, I want to make sure that is what others would recommend. I've got the program downloaded and see the command to rebuild. It will save the new library as "rebuilt library" in the pictures folder. Is this my best action?
    If I rebuild, shouId I then throw away my old "iPhoto Library", then change the name of the rebuilt library to "iPhoto Library"?
    What are the ramifications of rebuilding the library? Although I have a lot of albums, I only have a couple slideshows, only 1 web gallery item, and no cards. I assume I'll have to rename events; no big deal.
    I am a little surprised rebuilding the library is not built into iPhoto somewhere. Good thing someone wrote a program.
    Given this corrupted file, should I be checking my drive for other problems? Permissions are correct and the disk verified fine with disk utility.
    Thanks,
    Justin

    jcgraff
    Try these in order - from best option on down...
    1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library (Right Click -> Show Package Contents) allowing it to overwrite the damaged file.
    2. Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums back.
    3. If neither of these work then you'll need to create and populate a new library.
    To create and populate a new library:
    Note this will give you a working library with the same Events and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
    In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'
    Move the iPhoto Library to the desktop
    Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
    Go into the iPhoto Library (Right Click -> Show Package Contents) on your desktop and find the Originals folder. From the Originals folder drag the individual Event Folders to the iPhoto Window and it will recreate them in the new library.
    When you're sure all is well you can delete the iPhoto Library on your desktop.
    In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
    Regards
    TD

  • Corrupt Library6.iphoto - empty albums

    Hello, guys, hope someone out there is smarter than I (and smarter than "I-Photo").
    I have a corrupt library6.iphoto here. About 100 of my albums show zero pictures (only one is populated). But all 40Gb of photos are still intact in the 'Original' and 'Modified' folders. I believe the problem is a corrupt slideshow I just created. I think that because when I try to click that slideshow, iPhoto quits abruptly (i.e. no obvious way to delete it).
    I read this thread (and many similar) http://discussions.apple.com/thread.jspa?messageID=9861491&#9861491
    and the three options described there will cause a lot of work:
    Option 1. "Back-Up": My latest backup is about 15Gb ago (yes, that's a human error), and I've modified a lot of pictures since then, so I estimate I would lose about 20 to 30 hours of work.
    Option 2. "Rebuild": I'm in the process of rebuilding another 40Gb Library, but I guess it won't work since the corrupt Library6 file is a fraction of the size of my last backed up library6 file.
    Option 3. "Re-Populate": Not all the Rolls correspond to Albums, so there isn't an easy way to re-create my albums (another, 5 to 10 hours of work).
    My questions:
    A) Since I see the empty Album-structure intact in the corrupt library, is it possible that the album-data is still stored somewhere (despite the fact that the Library6 file is a fraction of what it was)?
    B) Is it possible to rebuild the libraries using all available photos in the Pictures folder? (i.e. using both folders 'Modified' and 'Originals'?)
    C) Is it possible to kick that slideshow out of the database, thereby leaving the empty Album-structure for me to re-populate?
    A thousand thanks to anyone who can help.
    -Stuart

    Stuart
    That library6.iphoto file is toast. There is no going back to it. Even if you could “repopulate” it somehow, you would be bringing data into an entity known to unstable - nothing too wise there
    As you don’t have an up-to-date- back up your choices are two:
    The first attempts to leverage the data about your albums mentioned here:
    A) Since I see the empty Album-structure intact in the corrupt library, is it possible that the album-data is still stored somewhere (despite the fact that the Library6 file is a fraction of what it was)?
    Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
    or
    Rebuild from Scratch.
    B) Is it possible to rebuild the libraries using all available photos in the Pictures folder? (i.e. using both folders 'Modified' and 'Originals'?)
    Yes, simply import the photos from both Folders. But you will have massive duplication as each will be treated as a new photo in itself. If you don’t have a working back up and/or if rebuilding with iPhoto Library Manager fails there is +no way+ to re-construct the relationship between the Original and Modified versions.
    C) Is it possible to kick that slideshow out of the database, thereby leaving the empty Album-structure for me to re-populate?
    No.
    To create and populate a new *iPhoto 6* library:
    Note this will give you a working library with the same Rolls and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
    Move the iPhoto Library to the desktop
    Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
    Go into the iPhoto Library on your desktop and find the Originals folder. From the Originals folder drag the individual Roll Folders to the iPhoto Window and it will recreate them in the new library.
    When you're sure all is well you can delete the iPhoto Library on your desktop.
    In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
    Regards
    TD

  • The PDF file and slideshow view corrupted using iPhoto. Macbook air only get corrupted slideshow and Mac Mini both slideshow and PDF file is corrupted.

    The PDF file and slideshow view corrupted using iPhoto. Macbook air only get corrupted slideshow and Mac Mini both slideshow and PDF file is corrupted.

    Saving as a PDF file for some users have been a problem.  If you boot into  Safe Mode and run iPhoto you can create undamaged PDF files.  We don't know why the problem but this is a workaround.
    This problem prevents many from ordering books, calendars and cards since iPhoto creates PDF file of them for uploading and printing.  Booting into Safe Mode lets them successfully order those items.

  • Corrupted Database Problem

    Greetings,
    I'm getting the following error running the base system installer:
    root@archiso ~ # pacstrap -i /mnt base
    ==> Creating install root at /mnt
    ==> Installing packages to /mnt
    error: GPGME error: No data
    :: Synchronizing package databases..
    core is up to date
    extra is up to date
    community is up to date
    error: database 'extra' is not valid (invalid or corrupted database (PGP signature))
    ==> ERROR: Failed to install packages to new root
    I've already tried updating the keyring:
    pacman-key --init && pacman-key --populate archlinux
    As well as changing around the mirrors in my mirrorlist and re-syncing with:
    pacman -Syy
    Running out of ideas and been scowering Google for an hour now with no result. Any help is appreciated. Cheers.

    bjornoslav wrote:Check the system time. Incorrect time and date cause problems with pacman because it can't verify the GPG keys properly.
    System time is fine.
    Also tried deleting the extra DB file, same error persists.

  • Replay logfiles on corrupt database

    I've got a machine here that has not been maintained very well. Someone with little knowledge of MaxDB has only kept Windows backups and no database backups. Also, there has been no LOG backups, everytime the log was full, someone just added another one :). Now one of the DATAvolumes is corrupt (it shows 0 kb) and the database won't come up. Everyone here is convinced that it won't come up ever again. Also, on top of all, the Windows backups aren't available anymore either. People feel sorry for it and just move on
    So now I've got some spare time and I want to take a closer look at it. I've got a corrupt database, and I've got a lot of LOG volumes (not backups). I'm not a MaxDB guru either, so I've got the following questions:
    Isn't it true that if you do not backup the database or the logfiles at all, all the database transactions committed after the installation still reside in the logfile(s)?
    With this in mind, couldn't it be possible to install the system just as it was right after the installation, and after that replay the existing logfiles? I've created a copy of the system where I can fool around. I've found lots of ways to recover a database with logbackups, but not with the logfiles itself.
    Isn't there anything I can do at all with the existing logfiles, with all the precious data in it? It has been a portal and there are (or were ) a lot of documents in it.
    Who can help me out?

    >Only thing is that the general idea was to build it again (by installing the system again) and replay all the later on added information (by replaying the existing logfiles).
    >I still find it strange that in fact all the data is there ( in the logfiles), but I cannot get to it.
    >Or I'm misinterpreting the whole logfile mechanism.
    Well - half and half I'd say.
    It's true, all changes to the database are logged to the log area.
    BUT (yes, a big BUT here), the critical point here is the starting point.
    To have all changes correctly applied, the database must be sure that the database  is really in the exact state like it was, when the log information starts.
    This synchronization is done via the restart_record and the log_info_page.
    In theory, if we would be able to generate a completely identical data area as it was, back then, when the history of log information began, then we would be able to recover the data.
    Just creating a new database won't do, since the db_create itself is not covered by redologs and ends up with a different data area each time (e.g. for each database a DB-Identifier with the timestamp of its creation is generated and saved).
    So, technically the only way I can think of would be to create a empty data area and than hack into the restart_record to fake the MaxDB into a recovery.
    If you are a MaxDB kernel developer you might be able to do that...
    regards,
    Lars

  • BerkeleyDB hangs trying to read corrupted database

    The provided corrupted database file causes reproducible hang in db->get method of Berkeley DB.
    Reproduced with Berkeley DB 4.8.30 and 4.3.29 under Linux.
    Corrupted database file: https://cfengine.com/bugtracker/file_download.php?file_id=123&type=bug
    Testcase:
    #include <db.h>
    int main()
    DB *dbp;
    DBT key, value;
    key.data = "x86_64";
    key.size = 6;
    db_create(&dbp, NULL, 0);
    dbp->open(dbp, NULL, "bdbtest.db", NULL, DB_BTREE, 0, 0644);
    dbp->get(dbp, NULL, &key, &value, 0);
    return 0;
    gdb backtrace:
    (gdb) bt
    #0 __memp_fget (dbmfp=0x602120, pgnoaddr=0x7fffffffe2ec, ip=<value optimized out>, txn=0x0,
    flags=<value optimized out>, addrp=<value optimized out>) at ../dist/../mp/mp_fget.c:293
    #1 0x00007ffff7aa94dc in __bam_search (dbc=0x603880, root_pgno=<value optimized out>,
    key=<value optimized out>, flags=<value optimized out>, slevel=<value optimized out>,
    recnop=<value optimized out>, exactp=0x7fffffffe41c) at ../dist/../btree/bt_search.c:753
    #2 0x00007ffff7a967a6 in __bamc_search (dbc=0x603880, root_pgno=<value optimized out>,
    key=<value optimized out>, flags=27, exactp=<value optimized out>)
    at ../dist/../btree/bt_cursor.c:2785
    #3 0x00007ffff7a98027 in __bamc_get (dbc=0x603880, key=<value optimized out>, data=0x7fffffffe5d0,
    flags=27, pgnop=<value optimized out>) at ../dist/../btree/bt_cursor.c:1088
    #4 0x00007ffff7b3e27f in __dbc_iget (dbc=0x0, key=<value optimized out>, data=0x7fffffffe5d0,
    flags=27) at ../dist/../db/db_cam.c:934
    #5 0x00007ffff7b4b250 in __db_get (dbp=<value optimized out>, ip=<value optimized out>,
    txn=<value optimized out>, key=0x7fffffffe600, data=0x7fffffffe5d0, flags=27)
    at ../dist/../db/db_iface.c:779
    #6 0x00007ffff7b4b57b in __db_get_pp (dbp=0x601a60, txn=0x0, key=0x7fffffffe600,
    data=0x7fffffffe5d0, flags=0) at ../dist/../db/db_iface.c:694
    #7 0x00000000004005df in main () at bdbtest.c:13
    --------

    Hi,
    Your database is corrupted, hence there is no surprise you cannot retrieve successfully from it:
    # db_verify -o cf_classes.db.duff
    db_verify: Page 4: btree or recno page is of inappropriate type 0
    db_verify: Page 4: totally zeroed page
    db_verify: Page 4: Btree level incorrect: got 0, expected 1
    db_verify: Page 3: unterminated leaf chain
    db_verify: cf_classes.db.duff: DB_VERIFY_BAD: Database verification failed
    Verification of cf_classes.db.duff failed.
    Dumping the database with db_dump -da shows the following where page 4 should have been:
    page 0: invalid: LSN [0][0]: level 0
         prev: 0 next: 0 entries: 0 offset: 0
    and a verification with a hex editor over the 4KB's of page 4, shows that this page is all 0s (zeros).
    You need to run recovery over this database. For backup and recovery procedures review the followings:
    - chapter 11 in the Berkeley DB Reference Guide, Berkeley DB Transactional Data Store Applications;
    - in the Getting Started with Berkeley DB Transaction Processing, the sections on Backup Procedures and Recovery Procedures.
    If your application is not using transactions (it is not set up as TDS, Transactional Data Store), you should review the section on Handling failure in Data Store and Concurrent Data Store applications.
    Regards,
    Andrei

  • Corrupted Database in Lightroom 3 Beta

    Can anyone offer any help how to recover from a "corrupted
    database" error on startup? It gives an option to repair, but it is unsuccessful. I was one who disregarded al the warnings about not using the beta for production, but I liked it so much that I just completed a huge wedding. Luckily, all my chosen files were exported as Jpegs but I have lost many, many hours of work. I also have LR2 which I had always used previously.

    Try your catalog back up file, just click to open the most recent and hopefully that will work and as long as you made regular back ups you should be OK. If all else fails import the files into a new catalog using the Beta and then update the files from the metadata (this will obviously only work if you save out the metadata. You can also do the same with LR 2 although if you used the new process version in LR 3 this will be lost.
    Using a Beat for production work is not a good idea, but at least if you backed up catalogs and wrote data out as xmp side car or directly to file if you converted to DNG you can always recover. If you did none of these things and used a Beta then you really are in trouble!

  • New mail messages not visible--"detected corrupt database" related?

    I am using Mail.app and an iPod Touch with an Exchange server (Intermedia). All of a sudden in the last few days, recent mail on the server is not visible using Mail.app or the iPod Touch. I have deleted the mail accounts on both devices twice and done an entirely fresh download of all mail on both, and the problem persists.
    Mail in the Inbox is visible. However, if I move an Inbox message to, say, Archive or Travel, then it becomes invisible--even though it is intact on the server and in its proper location there.
    I have also repaired permissions and run sudo daily/weekly/monthly maintenance processes, to no avail.
    In the console, I see the following error message. Could this be related and is there a way to fix it?
    Jul 17 11:14:36 xxx-xxxx-macbook Mail[108]: ISyncDataDirectoryCorruptedException: detected corrupt database while executing delete from Record
    Thanks for any help.
    Message was edited by: RKNYC

    Update: all messages are viewable in Entourage Exchange Web Services 2008, but not in Apple Mail, or in Mail on my iPod Touch, or after a new download of all mail on another Mac in Mail.app. Why is Entourage able to see all the messages while all the Apple Mail clients are missing them?

  • Possible Corrupt Database?

    I've been synching my Palm Treo 700p, iCal, and Entourage calendars on my MacBookPro, OS 10.4.8, and I think I may have a corrupt database. All the calendars have been set to delete events/meetings more than one year old, and none show any events earlier than one year ago, yet iSync keeps coming up and telling me I have hundreds of synch conflicts (most from 2004 and 2005). Can I delete the database without losing everything currently in my calendars? If so, which database do I delete?
    Thanks,
    Claude

    You cannot delete anything without forcing a corresponding deletion of matching records elsewhere on all of your applications, devices and servers.
    Given your brief description, it's likely that Entourage is the culprit. Isolate it from the remainder of your synchronization pool by temporarily disabling its connection to Sync Services, and see if the conflicts disappear. By reconfiguring sync clients, but not deleting sync records, you should be able to determine what is driving this conflict resolution process. Only by temporarily disabling or reconfiguring devices can you isolate the issue and resolve it.

  • DBF corrupted database

    Hey friends, I'm in great trouble here. 
    I'm using Microsoft Visual FoxPro 9.0 on my Windows 7 machine. I had some DBF files which was created in MS Visual FoxPro. The files were undoubtedly valuable since they contained my crucial data related to my office work. The files are now invalid
    therefore, inaccessible. I can't access any of my database files. Whenever I try to open one of them this comes in front of me: "File filename.dbf does not exist". 
    According to me this must be a file corruption error states the file is corrupted. I don't know how did it get corrupted. I'm dying to get these files back. Please help in this.
    Thanks in advance.

    It is not necessary to rebuild a corrupt database. All corrupt databases can fixed in less than one minute. 
    The solution is: Open database to main screen
    Copy the database but only one record(just pick a not recent record number at random; include "all", I usually name this database "FixMMDD" (( month Day))
    Open original database to mainscreen and append the FIXMMDD.dbf.
    You're done. 
    Occassionally you may have to update indexes. Very rarely are any records lost and when it happens those few records are clearly garbled.
    I've been doing this for three years with no problems.
    If you have fields that increment you'll have to adjust that for your last valid value.
    OTHERWISE
    I think those files of your which seem unreadable are corrupt. Just one thing always keep in your mind that corruption can make a file unreadable or useless. And due to this file becomes inaccessible. Any corrupt or damaged file can't be accessed
    until it gets fully repaired. All you need just remove the error from your DBF files and after doing this you can access those corrupt files. The data inside those files will be readable right after you repair them. You just need to consider
    about a software program or shall I suggest you about a tool which I have used? 
    Check this one: DBF Repair Kit
    It will help you as it helped me. Just try its demo version
    http://www.dbf.repair/ to see the preview of the content of the files which are unreadable.

  • Is there any way to restore or rebuild a corrupted database?

    I'm trying to get information from a database, but it's corrupted and not allowing me to see any availbable traces.  If there any way to restore or rebuild a corrupted database?
    Solved!
    Go to Solution.

    Here are a few screen captures of what I'm looking at.  The 3rd capture is of the files making up the database.
    Attachments:
    max_screen_capture.JPG ‏71 KB
    max_screen_capture2.JPG ‏67 KB
    max_screen_capture3.JPG ‏142 KB

  • Python + Miro from testing lead to corrupted database

    This update today was a killer. Miro just blew up and took all my channel metadata along with it to the tune of 'corrupted database'.
    It doesn't work even when I delete the .miro folder from my home. The thing errors out when I try to close it and stays open...
    OT: I've had a fair share of problems with Miro so I think it's time to look for something less bloated and less fragile. Any ideas?

    user3006396 wrote:
    Hi Experts,
    On one of the servers with Windows Server 2008, we have 5 Oracle 11g databases installed for our dev & testing environments.
    With the help of oracle client we are connecting to those server db's.
    Last Friday,for one of the db's, I have populated a million records to few tables and everything was fine on that day.
    Suddenly on this Monday, one of the front-end users complained that the db was not working. We are not able to connect to that db, but able to connect to one of the other db's on the same server.
    Message thrown was :
    " ORA-12514: TNS:listener does not currently know of service requested in connect
    descriptor "
    I connected to server and tried to login from there..the same message was thrown, but able to connect to other db's.
    Finally I set the oracle_home path to the db to which i was not able to login and connected using
    something like....
    conn /as sysdbaidle instance
    startup;database mounted
    database started
    After that i was able to connect to that db as well as all other db's on the server.
    My doubt is, why suddenly that stopped working and it didn't work until i use "startup" command ?
    Also, how DBA's maintain server's with multiple oracle_home's?(though recommended to have multiple schema's instead of multiple db's)
    I'm the only Oracle guy in the team and need to take care of everything(basically i'm developer and new to DBA related tasks)
    My lead's warned me to make sure that it won't happen again !!
    Thanks guys.. you are always awesome in giving nice suggestions.find alert_SID.log file post excerpt showing entries from period just prior to the DB STARTUP.
    it appears the instance went missing.
    Hopefully the log file will have clues as to why it went away.

  • New to iPhoto: Database Corruption and iPhoto Package

    Coming from the PC I'm used to individual files with Picasa and Photoshop and I'm confused about a few things:
    1. Is the iPhoto database separate from the iPhoto package file that stores all of the images?
    2. And if you were to lose your database because of corruption, do you lose all of your individual photos?
    3. Or if the package somehow became corrupted, do you lose your original images?
    4. Slightly off-topic -- does Aperture store the images separately or does it use the same "database package" concept as iPhoto?

    1. Is the iPhoto database separate from the iPhoto package file that stores all of the images?
    Yes and No. It depends on the settings you choose. In the default setting both the photos and the database are contained within the Library Package. For more see below*.
    A Package File is simply a folder that looks like a file in the Finder. The change was made to the format of the iPhoto library because many users were inadvertently corrupting their library by browsing through it with other software or making changes in it themselves.
    Want to see inside? Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
    Standard Warning: Don't change anything in the iPhoto Library Folder via the Finder or any other application. iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
    2. And if you were to lose your database because of corruption, do you lose all of your individual photos?
    No. The db is a couple of files inside the Library. The photos are at no more risk that when a file goes bad in any folder.
    3. Or if the package somehow became corrupted, do you lose your original images?
    There's no way for a package to become corrupted. Like I say, it's just a folder.
    Of course, the protection for any data on your computer is a good up-to-date back up.
    4. Slightly off-topic -- does Aperture store the images separately or does it use the same "database package" concept as iPhoto?
    Yes and no. Depends on the settings you choose.
    * And this is the below piece to see:
    There are two kinds of Library: Managed and Referenced.
    A +Managed library+, is the default setting, and iPhoto copies files into the iPhoto Library when Importing. In this scenario iPhoto is responsible for File Management.
    A +Referenced Library+ is when iPhoto is NOT copying the files into the iPhoto Library when importing because you made a change at iPhoto -> Preferences -> Advanced. In this scenario you are responsible for the File Management.
    *How to do it:*
    Simply go to iPhoto Menu -> Preferences -> Advanced and uncheck 'Copy Files to the iPhoto Library on Import'.
    *What Happens:*
    Now iPhoto will not copy the files, but rather simply reference them on your HD. To do this it will create an alias in the Originals Folder that points to your file. It will still create a thumbnail and, if you modify the pics, a Modified version within the iPhoto Library Folder.
    *Some things to consider:*
    1. Importing and deleting pics are more complex procedures. You have to to put the files where they will be stored before importing them. When you delete them you'll need to remove the files from the HD yourself.
    2. You cannot move or rename the files on your system or iPhoto will lose track of them on systems prior to 10.5 and iPhoto 08. Even with the later versions issues can still arise if you move the referenced files to new volumes or between volumes.
    3. Most importantly, migrating to a new disk or computer can be much more complex.
    4. Because iPhoto has no tools for managing Referenced Files, if, for some reason, the path to the photos changes then you could find yourself resolving aliases for +each photo in the Library+ one by one.
    My own opinion:
    I've yet to see a good reason to run iPhoto in referenced mode unless you're using two photo organiser
    If disk space is an issue, you can run an entire iPhoto Library from an external disk:
    1. Quit iPhoto
    2. Copy the iPhoto Library as an entity from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    If you're concerned about accessing the files, There are many, many ways to access your files in iPhoto:
    You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Command-Click for selecting multiple pics.
    Uploaded with plasq's Skitch!
    You can access the Library from the New Message Window in Mail:
    Uploaded with plasq's Skitch!
    Many internet sites such as Flickr and SmugMug have plug-ins for accessing the iPhoto Library.
    If you're using Gmail you can use iPhoto2GMail
    If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
    If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
    *If you want to access the files with iPhoto not running*:
    For users of 10.6 and later:
    You can download a free Services component from MacOSXAutomation which will give you access to the iPhoto Library from your Services Menu. Using the Services Preference Pane you can even create a keyboard shortcut for it.
    Other options include:
    1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
    2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
    3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
    *Using iPhoto with Photoshop*
    You can set Photoshop (or any image editor) as an external editor in iPhoto. (Preferences -> General -> Edit Photo: Choose from the Drop Down Menu.) This way, when you double click a pic to edit in iPhoto it will open automatically in Photoshop or your Image Editor, and when you save it it's sent back to iPhoto automatically. This is the only way that edits made in another application will be displayed in iPhoto.
    Note that iPhoto sends a copy+ of the file to Photoshop, so when you save be sure to use the Save command, not Save As... If you use Save As then you're creating a new file and iPhoto has no way of knowing about this new file. iPhoto is preserving your original anyway.
    Aperture - which is somewhat more expensive that iPhoto - has much better tools for running Referenced Libraries. I have no reservations about running Aperture in that mode.
    Regards
    TD

  • Corrupted Library6.iPhoto file.  New Library from ext. drive?

    My Library6.iPhoto file is corrupted. How do I create a new 'Library' when all the 'original' stills are on an external drive and will not fit on my 'desktop'?
    Ben

    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
    Do you Twango?

Maybe you are looking for