I originally developed this file in 8.5 Adv but recently started using 9 Adv for maintenance and new development. I have an older database, (dev'd in 8.5), with a date field where you can enter a date such as: 5/19/2008 and it will display as May 19, 2008. This display is okay but the strangest thing happening is that this field is somehow locked into displaying a wrong date! It is showing "May 8, 2008". I can enter and change the date in the field but it always displays "May 8, 2008". Any ideas what is happening? :

Have you checked to see if there is a second field there ontop of it perhaps grouped together?

What happens when you click into the field?

Also double check your date format options.

Sorry it took so long to provide some feedback. Stuff happens, right? I double checked as you sugested but everything looked okay. However, I played around some more: First I changed the date field to display as entered in the data entry form view. Next, I removed the date field from inside the text box of my Form Letter view and placed it separately and above the text box. I formated the field to display the way I want it to. And lo, it worked. Putting the field and specifying a certain type of formatting for the date does not work inside a text box. Go figure.

Thanks for your help.

Putting the field and specifying a certain type of formatting for the date does not work inside a text box.

It does work, but you are only allowed one date format for the entire text object, so that ALL date fields merged within the same text object will be displayed using the same format. The formatting itself needs to be done while the entire text object is selected.

However, I am not aware of a way to format a date field to display the wrong date, as described in your original post.

Yes, I agree about the date formatting but as you imply it doesn't make sense why a wrong date would be posted there. Additionally, not matter what date you enter in that field in the data entry form, it always prints out with that one specific date. However, as I said, when I took that field outside the text box it worked just as it should with the correct date. Go figure. :shocked:

Hi

I don't know why but I think that that field wasn't a merge field... Was it ?

I'm curious to see ... can you post a file showing that problem ?

I'd be interested in seeing it too.

Afterthought:

One thing that could explain this is that the field comes from a related TO.

Edited June 4, 200817 yr by Guest