One thing I'll share that caused us a weird issue regarding "time".  All my 
clients
use this time format:
    TIME format     HH:MM:SS
    TIME sequence   HHMMSS

 At one of them, we started having a problem where an old program would
select a Max(datetimecolumn) from a table, and then do an "edit using <form>
where datetimecolumn = .theValue".  And it all of a sudden started failing.  

It took a "bug" report to RBTI for them to point out what my problem was!
The time settings had changed to this:
    TIME format     HH:MM AP
    TIME sequence   HHMMSS

 

Using 9.5's "find in forms" feature, I found that another programmer on the job 
had used some RRBYW code that had specified that time format!  So there 
was a mismatch between the sequence and the format and that prevented the
"where" clause from working.  Whoopsy!

Karen


 

-----Original Message-----
From: A. Razzak Memon <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Sun, Jan 12, 2014 6:34 pm
Subject: [RBASE-L] - Re: Datetime issue


At 06:41 PM 1/11/2014, Tom Hart wrote:

>That is what I did different, I copied from your earlier post but
>somehow the set time format was HH:MM:SS, I have that resolved now.

Tom,

I am glad to hear that.


>Why does that affect the datetime stamp?

For your education ...

Every UNLOAD routine (except AS ASCII), always carries the native
settings as follows:

CHARACTER Settings
    BLANK
    DELIMIT
    LINEEND
    SEMI
    QUOTES
    PLUS
    SINGLE
    MANY
    IDQUOTES
CURRENCY Settings
    SYMBOL
    PREF and SUFF
    Subunit Digits
    FORMAT
Operating Conditions
    CASE
    AUTOSKIP
    REVERSE
    BELL
    TOLERANCE
    ZERO
Special Character
    NULL
DATE Settings
    YEAR
    CENTURY
    SEQUENCE
TIME Settings
    SEQUENCE

These settings are enforced to assure the successful LOAD of the
unloaded file.

So, when you are loading and implementing someone else's form,
external form, label, report, or table/view structure, after a
successful load, it is your responsibility to verify and reset
your database settings, if necessary. Thus, the need to enforce
all default settings in your startup application file, as
suggested in my earlier reply.

Very Best R:egards,

Razzak.

www.rbase.com
www.facebook.com/rbase
-- 
31 years of continuous innovation!
16 Years of R:BASE Technologies, Inc. making R:BASE what it is today!
-- 



 

Reply via email to