Jump to content

BoatDriver

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About BoatDriver

  • Rank
    newbie
  1. Cloning the file worked...auto-entered times are now entered correctly. Interestingly, in the corrupted file, all auto-entered times *were* being changed from PM to AM on committing the record... Thanks very much for the idea of cloning the file, as I had convinced myself that I had some setting wrong that I just couldn't find.
  2. It's a new file I've been working on for about 2 weeks, with just a few junk records in it. I'll try cloning it and see if I can reproduce the problem. It was created under the current system, on the current machine. The thing is, it's like FM is actually changing the data, not just the display format... 16:xx:xx is becoming 04:xx:xx.
  3. After some testing, there's something really weird going on here... I created 3 new fields... Time - simple time field ModTime - Timestamp field, auto-enter timestamp TS - simple timestamp field All field are placed on layout & set to leave dates & times displayed as entered. My system is set to use hh:mm:ss format in international system prefs. FM prefs are set to "Always use system formats". When I type command-; in Time field and commit the record.... Time displays "16:34:20" ModTime displays "2/6/2006 04:34:20" When I type command-; in TS field.
  4. I have a file I've been working on in FM8 that auto-enters the modification time for a record exactly 12 hours off the correct time. I've tried checking all the time formatting for the field in layout mode, double checked my system clock, etc., to no avail. I've even created a garbage file to test the auto-enter function, and it gives the correct time in this file, but I still can't find the problem in the original file. Any insight anyone has would be appreciated, as this is driving me nuts, not to mention wasting a huge amount of time!
  5. I'm having the exact same trouble in Dev 7.03 & OSX 10.3.8. I've tried moving around the script steps, & even writing a temporary test script, but it always flashes the "print" layout when I call the print step. It's like the print step is forcing a refresh regardless of a previous freeze step.
  6. I'm having the exact same trouble in Dev 7.03 & OSX 10.3.8. I've tried moving around the script steps, & even writing a temporary test script, but it always flashes the "print" layout when I call the print step. It's like the print step is forcing a refresh regardless of a previous freeze step.
  7. I'm having the exact same trouble in Dev 7.03 & OSX 10.3.8. I've tried moving around the script steps, & even writing a temporary test script, but it always flashes the "print" layout when I call the print step. It's like the print step is forcing a refresh regardless of a previous freeze step.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.