Re: Witango-Talk: Mac OS X Timestamp issue: Found Problem.

[Robert Garcia]

Yes, in my testing, it did change them ALL, but it was the timestamp that was throwing the error. I have thought about writing an application that would read in a taf, check for the !CST, and if exists, connect to the specified DSN, and fix the datatypes. I have it worked out in my head, but I don't know when I will find the time, it would probably take me 2-3 days of coding. I think the best thing to do on this, is for someone to try to figure out why it doesn't do it on my system, but on others, or is there a technique I use when creating inserts/updates and the like, where it doesn't happen, I just don't know. But I think it is safe to say it is definitely a bug in the studio, and hopefully support will let us know they are working on a fix. --  Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Jul 15, 2005, at 5:31 PM, MJPinckard wrote: I see the same thing on the timestamp data dictionary, only variation on reported, is that if I edit the action, I get DataType="!CST" on every column, not just the date column... it's just that the date column is the only one to fall over if I don't manually correct it in BBEdit, so I've been leaving the others as is. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf