Incorrect date created

I have some old documents from the OS9 days that have invalid 'date created' metadata .. i.e. some say they were created in 1934. Is there a way to modify this without going into terminal? A shareware program hopefully?

Take a look at this thread:
http://discussions.apple.com/thread.jspa?messageID=5433260&#5433260
The program mentioned "A Better Finder Attributes" seems to work fine, even if you don't bother adding the Contextual Menu item nor the Prefs pane (which I elected not to add, who needs more clutter in either when you need to use the program once in a blue moon?).
Francine
Francine
Schwieder

Similar Messages

After upgrading to elements 12 the metadata shows incorrect date created?

After upgrading from elements 8 to 12 all the pictures in the album have a new date created in the metadata the is the date I upgraded. this is incorrect because the picture was not created on this date but moved or updated. This is a problem when running things like screen savers that go by date created. How do I fix the metadata to reflect the actual date the picture was created?

After upgrading from elements 8 to 12 all the pictures in the album have a new date created in the metadata the is the date I upgraded. this is incorrect because the picture was not created on this date but moved or updated. This is a problem when running things like screen savers that go by date created. How do I fix the metadata to reflect the actual date the picture was created?

Bridge CS5.1 metadata show wrong "Date Created". It is always June 1, regardless of file examined.

Bridge CS 5.1 metadata shows incorrect "Date Created". It shows June 1, no matter when the file was actually created.

smilin Mike wrote:
…The purge cache operations…
Try always to Purge the Cache through the Tools Menu in Bridge. The global Purge Cache has been broken for years, at least through Bridge CS4. Don't have CS5.
Wo Tai Lao Le
我太老了

"Date Created" incorrect in Finder after copying image files from CF reader

Whenever I download image files (by drag and drop copying) from a CF card reader, the 'Date Created' info incorrectly defaults to 'Dec 31, 1903' in the List view of the Finder window.
'Date Created' shows up blank in the File Info window, too. Correct file info does however show up in the copied Meta Data.
I've only been able to transfer correct 'Date Created' info by using Image Capture, which is pretty annoying.
I've tried several cameras, CF cards, USB & FW card readers, and Macs running both Panther and Tiger. Same problem all around. Interestingly, files copy without a problem onto a PC.
I'm a photographer and I need to sort my images by 'Date Created' because I often shoot with two cameras and need to know the chronological order in which photos were taken.
Ideas anybody?
G5 Mac OS X (10.3.9)
G5 Mac OS X (10.3.9)
G5 Mac OS X (10.3.9)

stqn wrote:
photorec ?
Edit: I see that testdisk and photorec belong to the same package... Still it looks like it should be the right tool for the job; but I might be wrong as I never used it.
Used it a couple of times, my daughter wiped photos from her mobiles memory card by accident .... Linux to the rescue
Last edited by Mr Green (2010-12-21 11:01:01)

Unable to stop incorrect date exports

How do we set up a form in Adobe Acrobat XI that allows dates to be formatted a certain way (mmm/dd/yyyy) and exported in the same way to Excel and always be recognized as a "proper" date in Excel?
Currently the following does not work (Attempt #1):
Set up a field; Set the format category as date; Set up a Custom format of "mmm/dd/yyyy"
Create a distribution file
When users fill out the form if they type in an incorrect date, eg., "August 27 2013", the form automagically shows the date on the PDF as "Aug/27/13" - Great!
When the users submit the form and it's brought into the response file the dates are shown in a default date format of mm/dd/yyyy - Fine, once the form owners understand this
When the form owners export the information the data exported is the same as the original users entered it, not as it was automagically formatted to. For instance, if submitters originally entered "August 27, 2013" then that's what goes across to Excel. And some of these formats Excel doesn't know how to convert. - Understandably frustrating for form owners
Attempt #2: As a workaround we set up special formatting that has a mask of "AAA/99/9999". This at least provides forces the users to use the same formatting, but is confusing the submitters when they need to enter dates from 1-9 and we've also found that the conversion of this format to a date in Excel doesn't work, but at least it's consistent! Javascript was also added to force users to use specific month abbreviations.
d = new Date(event.value.replace(/-/g, " "));
if (!Date.parse(d)){app.alert("Please enter in a proper date.\n\nThe month abbreviations are: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec");}
Attempt #3: The last attempt was to continue to use the set up as Attempt #1, but to also use the javascript from Attempt #2. The theory being that if a user entered in "August 27 2013" the javascript would complain. Alas, the javascript appears to run after Adobe automagically does its date format conversion.
Does anyone know how to get around this or have any other ideas to either enforce a usable date format or have Adobe export the dates as they've been automatically formatted to? We've tried to find a way to turn off the automatic date conversion that Adobe's running, but haven't found a way yet. Another option seemed to be to allow a masking that allowed for optional characters (so that the "0" wouldn't be needed for the dates 1-9) but there doesn't seem to be one.
Thanks in advance!

Since there was no clear way to ensure that the date formatting was correct prior to exporting, we're going to get the respondants to use drop downs to ensure the formatting is correct. Not the most convenient for the users though as they're accustomed to being able to type in the values to select it (e.g., for the date of 23 they would expect to enter 2 then 3 for 23) based on other applications, but the Adobe pull downs don't "group" what's been entered (e.g., 2 then 3 will select 30, not 23) and so it will take them a bit to get used to it. I still can't believe that Adobe wouldn't simply export what it's been formatted to though... after all that's what we set the form up for.

Crystal report showing Incorrect data against Bex Query

I have created Crystal report on top of Bex Query, I have not done any calculations in the report, just dragging structure and key figure in the report, ran for one month, when I compare with Bex Query with same period, it is showing incorrect data.
I don't know what can be wrong here?
We are Business Objects 3.1 SP3.
Thanks,
Ravi

HI,
I would suggest you trace the workflow in Web INtelligence according to these notes:
Tracing:
Unix : Note 1235111
Windows : Note 1260004
and then post a link for downloading the trace files here.
regards
Ingo

BOXIR2 FP4.6 -WebI report with merged dimensions: Incorrect data

Issue: BOXIR2 FP 4.6 -WebI report with merged dimensions: Max value of an object from second query is displayed in the report even when the formula is based on the object from the first Query.
Data displays properly on BOXIR2 SP2.
Steps to reproduce.
1.Use u2018Island Resort Marketingu2019 Universe to create a WebI report.
2. Create a Query with objects u2018Reservation Dateu2019 and u2018Future guestsu2019 and apply a query filter where the u2018Reservation Dateu2019 is between 1/1/2001 and 31/1/2001 an Run the query.
3. Add a second Query with the same objects i.e. u2018Reservation Dateu2019 and u2018Future guestsu2019 and apply a query filter where the u2018Reservation Dateu2019 is between 1/1/2001 and 31/12/2001.
4. Create a report variable MaxDate using the syntax "=Max([Query 1].[Reservation Date]) In Report"
5. Use the objects u2018Reservation Date Query 2u2019, u2018Future guests Query 2u2019 and u2018MaxDateu2019 variable to create a table in the report.
You will find the Maxdate column displays Max date values of u2018Reservation Date Query 2u2019 instead of u2018Reservation Date Query 1u2019.
Could you please advice me on this issue.

Hi Hiteshwar,
MaxDate variable returns a maximum of Reservation date from Query 1 i.e. 1/15/01 which is correct. If you put that variable separately it will display that date correctly but you are grouping it along with objects from the query2 thatu2019s why it is displaying correct value for Query 2 where it finds 1/15/01, but for other values WEBI canu2019t group this value as it refers its formula which contains Query 1 reservation date.
Hence we canu2019t say it is displaying values from Query 2 it is taking values from Query1 itself for 1/15/2001 and for remaining values it is taking non matching values from Query 2 with which it is grouping.
If you put that variable with objects from Query1 it wonu2019t display 1/15/01 but all values reservation date from query 1 contains because it is grouping based on reservation date though it is single max value.
Even when you write "=Max(Query 2.Reservation Date) formula and use it with objects from query 1 though it contains so many values it matches (Groups) only the values from reservation date from Query 1.and displays only those values i.e. 1/1/2001 and 1/15/01.
MaxDate returns 1/15/01 as Maximum Date value from Query 1 but Query 2 contains value far more greater than 1/15/01 hense that will be more incorrect data if WEBI displays maxdate as 1/15/01 along with Query 2 objects.
Here we can avoid this behavior by Custom SQL but MaxDate is a report level variable hence we canu2019t edit SQL.
If your data contains some duplicate values WEBI will repeat MaxDate value like
Reservation date     Restaurant           Future_Guests    Total Guests
1/1/01                          ABC                         3                   3
1/15/01                       XYZ                          4                   8
1/16/01                       XYZ                          4                   8
By default, WEBI Groups Total Guests based on the Restaurant and Reservation Date, but if we want we can group those values based only on Restaurant which will duplicate Total Guest values for Restaurant XYZ. But you report contains only one dimension with all unique Values we canu2019t group those.
I hope this is clear.
Thanksu2026
Pratik

Date Created files are listed as 12/31/1903 ???

All my files and folders listed under: Date Created has incorrect dates of Descember 31, 1903. Files under Date Modified are correct. System files and apps are also not affected.
These incorrect dates are on my internal drive and also on my PC backup servers.
Questions:
- What is the cause?
- How to correct?
- Most important. Are these files in any kind of jeopardy for corruption.
Thanks

Or the files are missing the creation date in the directory structure, maybe because they've been to another platform and back.
The original Macs use 1st Jan 1904 as the base date from which all other dates are calculated. Unix uses 1st Jan 1970 (the "epoch"), Windows might use 1900.
So it sounds like the creation date has been filled out with high value, producing the 2's compliment effect you're seeing, setting the date to just before the earliest value it could be, In effect, the creation date is being seen as a slightly negative number, perhaps -1.
This would reinforce my belief that the files have been to another OS that doesn't know about storing creation dates. This, of course, might just be OS9 or earlier, rather than anything like Windows or OS/2.
Where were these files originally created ?

Date Modified & Date Created- All the same date

I have somehow caused all my "Date Modified and Date Created" to have the same date (Month-Day-Year & Time) for all the folders and every piece of work I have in them. How do I get all my files to read their original date created/ modified and saved back again. It's important for the work I do.
Thank you
Vietvet68

I, too, have "date" problems on my MacBook (with operating system Mac OS X). We just got the computer this month and had the Genius Bar download much of our files from our old Dell computer. The problem is that every date is incorrect, from the Created date to the Modified Date. For instance, here are some interesting dates: "Created 2/6/40" or "Modified 1/18/38." Now, the computer SHOULD know that these dates are well into the future. I checked out Preferences, and the date setting is correct. But somehow the Mac system screwed up all the Created and Modified dates on ALL the files it copied from our Dell, and even the current dates (such as the Modified date noted above) have years into the future. If you cannot set the dates correctly in Preferences, where in heck CAN you set them--and why is the Mac making up such odd dates?? Thanks!

Why do I have files with Date Created of Feb 5, 2040?

I have at least 26 documents with Date Created shown as Feb 5, 2040 10:28 PM.
The Date Modified seems to be okay, ranging from 9/24/00 to 10/29/12 - except for one that's 12/31/69.
The Get Information window shows the same dates as the normal Finder window.
File types are mostly DOC with some JPG and PDF and one TIFF.
All were created by me over the course of time on a succession of Macs (except for that 12/31/69 PDF, which was downloaded from Garmin) and then migrated.
Those I've checked have a Last Opened date that's the same as the Date Modified date.
These documents are all in my Documents folder, in two subfolders, with some of them further down a hierarchy of subfolders.
I first noticed this a few weeks ago.
The number of these 2/5/40 documents seems to be increasing.
Does anyone know:
What could cause this phenomenon?
How can I stop it?
It's not a big problem per se, but is it likely to cause other problems?
Is there a way to correct the Created Date?
Thanks for any help!

Then I may only guess that perhaps the date was off at some point in time that coincided with when those files were created or the application that created them has a bug in it.
Oh, at this point in time are all new files dated incorrectly? If so then there could be a corrupted part of the PRAM. You might try Resetting your Mac's PRAM and NVRAM.

Date created. Date file created

I am on WIndows 7, and I just got a few mpeg clips captured with Premiere pro cs6
I would like to know WHEN were these senes shot, so how can I do this.
Presently in metadata of the Bridge the Date created / Date file created / Date file modified are the same (today's date)
In case that it cannot be done on Bridge, is there a simple utility that will give me the info

The preferences are selected correctly, but as stated, in Bridge I see the same date for Date created / Date file created / Date file modified
I was told that the scenes were shot last month, therefore the dates shown in Bridge are incorrect.
Now, I am not sure what camera and/or cameras were used and under what conditions, so I am wondering if there is a way to determine the correct dates

Incorrect dates in Moments

I have recently synced quite a few photos, old and new, onto my iPad (iOS 7.1.2) using iTunes (11.3.0.54) on my Windows 7 machine and not all, but some photos are appearing in Moments under the wrong date.
After checking (and changing if needed) the Date Taken, Date Created, Date Modified and Date Accessed for the photos and the folder each group of photos are in, some are still appearing under the incorrect date.

photo_journ wrote:
Oh that's brilliant. Thanks very much. Worked like a charm.
Does that indicate any other underlying problem with the user account?
no. just some minor corruption in the preference file with the date settings. we deleted it and it was recreated from scratch with default values.
I just tried loading some CDs that were burnt on an older PowerBook Pro and the Macbook Pro wont read any of them -- all the same brand. Other brands it reads fine so I'm wondering if the dates might issue might indicate an underlying problem?
this is quite unrelated to the date issue. it could be a bad CD brand - can easily happen with some cheap ones. or there could be something wrong with the burner on the powerbook. can you read those CDs on other computers?
I left this open in case you have any more information you would like to add - even about the fix for the dates. Otherwise feel free to close it.
as the thread starter you are the only person one who can close this thread.
Thanks again. It was annoying.
John

IPhoto problem with "date created" on photos when moving to Ext HD

I'm unable to copy or backup photos from iPhoto onto an external HD w/o iPhoto changing the original date and time information for the photos. I've exported them and dragged them, with different results, but the "date created" changes every time. It changes the date the original photo was taken (which is displayed for each photo in iPhoto), either changing it to the date that I edited the photo or the date that I moved the photo onto the Ext HD. Any solutions?

Thanks for the responses, Larry and Terence.
I understand that there is a difference between the photo date and the file date, and I think I understand what is going on when I try to copy my photos onto my External HD. What I don't understand is why the EXIF data from each photo can't be transferred along with the photo. The only date information that comes with it (via Finder) is the following:
1) If I drag photos into a file I've named and created on my ExtHD, finder changes the "date created" from the date the photo was taken to the date that I moved the photo from my laptop onto my destop Mac, not the date that the photo was taken.
2) If I use the export function to attempt to put photos on my ExtHD, finder changes the "date created" and the "date modified" to the current date and time on every photo. (And who would even want that information?)
What I want is for each photo to display the date and time that I actually TOOK the photo. Is that so hard to do?
Why does Finder switch to some sort of filing date instead of keeping the EXIF data that it seems most people would prefer?
I hate to say this, but when I had a PC this was as easy as pie. No problems, EVER. And now that I have a Mac, my photo library on my ExtHD (where I store my photos for safekeeping -- in addition to Time Machine) is a mess. My folders display the date, but the photos inside each file are incorrectly dated.
Melinda
P.S. I have Mac OS X, Version 10.5.8, and would need the 10.6 version or higher to use the Better Finder app that Terence mentions. Do you think I should update to get that program? Is that program free or do I have to pay for it? Would that solve my problems?

Can't sort by date created in Bridge

I have raw files from two photographers that covered the same event. When I combined them in a folder in Bridge and apply view >sort>by date created, the images are only arranged in chronological order within each photographer's photos and not as a whole. How can I get both groups of photos to sort together by date created?

It should work as you expected, that is if both have correct time settings
in their dSLR set.
First try the purge cache for folder option, while pointing Bridge at the
problem folder go to the menu tools/cache/purge cache for folder and let the
cache build again for the files in this folder before you give it a try.
How can I get both groups of photos to sort together by date created?

Incorrect data in ODS

Hi All,
we are loading data from one ODS to another with delta processes.The second ODS got some incorrect data Populated.After that I did a full repair load selectively for one record only from first ODS to another and it went fine.But when I am loading by full repair load the records for entire company code,one particular key figure is getting doubled for most of the records.I've checked there is no problem with the start routine.
Please let me know if I am missing anything in full repair load.
Thanks in advance.

Hi,
In sequence to this post,now i am getting a differnt and strange error.
the data gets loaded from ODS1(0FIA_DS11) to ODS2(0FIA_DS12).
But for some asset main nos the CACQ_VL_YR and TACQ_VL_YR does not get populated.
WE have a start routine in between.The start routine poplualtes the CACQ_VL_YR .TACQ_VL_YR is polulated with ACQ_VAL_TR.
the routine is as follows:
DATA: lt_trans LIKE table of DATA_PACKAGE,
         wa_trans LIKE LINE OF lt_trans.
LOOP AT DATA_PACKAGE.
    CLEAR wa_trans.
Nicht-Werfelder 1:1 übernehmen
    MOVE: DATA_PACKAGE-currency   TO wa_trans-currency ,
          DATA_PACKAGE-comp_code TO wa_trans-comp_code ,
          DATA_PACKAGE-/BIC/ZASS_MAIN TO wa_trans-/BIC/ZASS_MAIN ,
          DATA_PACKAGE-/BIC/Zdep_area TO wa_trans-/BIC/Zdep_area ,
          DATA_PACKAGE-fiscyear   TO wa_trans-fiscyear,
          DATA_PACKAGE-fiscvarnt TO wa_trans-fiscvarnt.
Wertfelder mit identischer Übertragungslogik bei PLN und ***
    MOVE:
    DATA_PACKAGE-vaw_odp_tr TO wa_trans-vaw_odp_tr,
    DATA_PACKAGE-vaw_sdp_tr TO wa_trans-vaw_sdp_tr,
    DATA_PACKAGE-vaw_udp_tr TO wa_trans-vaw_udp_tr,
    DATA_PACKAGE-vaw_avr_tr TO wa_trans-vaw_avr_tr,
    DATA_PACKAGE-va_rapc_tr TO wa_trans-va_rapc_tr,
    DATA_PACKAGE-va_rodp_tr TO wa_trans-va_rodp_tr,
    DATA_PACKAGE-va_invs_tr TO wa_trans-va_invs_tr.
    CASE DATA_PACKAGE-transtype.
      WHEN '***'.
    Wertfelder kumuliert
        MOVE:
        DATA_PACKAGE-acq_val_tr TO wa_trans-cacq_vl_yr,
        DATA_PACKAGE-inv_sup_tr TO wa_trans-cinv_gr_yr,
        DATA_PACKAGE-ord_dep_tr TO wa_trans-cor_dep_yr,
        DATA_PACKAGE-spc_dep_tr TO wa_trans-csp_dep_yr,
        DATA_PACKAGE-upl_dep_tr TO wa_trans-cup_dep_yr,
        DATA_PACKAGE-res_trf_tr TO wa_trans-cres_tr_yr,
        DATA_PACKAGE-interst_tr TO wa_trans-cinter_yr,
        DATA_PACKAGE-reval_tr   TO wa_trans-crev_rv_yr,
        DATA_PACKAGE-rev_odp_tr TO wa_trans-crev_od_yr.
        COLLECT wa_trans INTO lt_trans.
    Wertfelder geplant
      WHEN 'PLN'.
        MOVE:
        DATA_PACKAGE-acq_val_tr TO wa_trans-acq_val_tr,
        DATA_PACKAGE-inv_sup_tr TO wa_trans-inv_sup_tr,
        DATA_PACKAGE-ord_dep_tr TO wa_trans-plo_dep_yr,
        DATA_PACKAGE-spc_dep_tr TO wa_trans-pls_dep_yr,
        DATA_PACKAGE-upl_dep_tr TO wa_trans-upl_dep_yr,
        DATA_PACKAGE-res_trf_tr TO wa_trans-pln_avr_yr,
        DATA_PACKAGE-interst_tr TO wa_trans-pln_int_yr,
        DATA_PACKAGE-reval_tr   TO wa_trans-prev_rv_yr,
        DATA_PACKAGE-rev_odp_tr TO wa_trans-prev_aodyr.
        COLLECT wa_trans INTO lt_trans.
   'echte' Bewegungen ignorieren.
      WHEN OTHERS.
    ENDCASE.
ENDLOOP.
DATA_PACKAGE[] = lt_trans[].
if abort is not equal zero, the update process will be canceled
ABORT = 0.
Can anyone throw some light on this?
Regards,
Dhanya.

Incorrect date created

Similar Messages

Maybe you are looking for