Hmm
 
I checked for a function to use here, but there's only ones for hours, minutes and seconds, not thousandths of seconds.
 
Forgive me for being pushy - but if you need a unique identifier, what's wrong with an autonumbered integer column?
 
At any rate, the method you're using to post the value in the column is an old 6.5++ technique. Have you tried the PROPERTY command in an EEP to see if it works any better?
 
PROPERTY TABLE tablename 'EDIT'
PROPERTY ComponentID TEXTVALUE .varname
SAVEROW
 
If this doesn't do it, may be time to report to RBTI as a bug or enhancement request.
 
David Blocker
[EMAIL PROTECTED]
781-784-1919
Fax: 781-784-1860
Cell: 339-206-0261
----- Original Message -----
Sent: Friday, December 31, 2004 11:51 AM
Subject: [RBG7-L] - Re: TIME IN THOUSANDTHS


Nope.  Did not do the trick in the row.  the variable at the R: is correct, still.  The row still shows 000 for the thousandths.


"David M. Blocker" <[EMAIL PROTECTED]>
Sent by: [email protected]

12/31/2004 11:25 AM

Please respond to
[email protected]

To
[email protected] (RBG7-L Mailing List)
cc
Subject
[RBG7-L] - Re: TIME IN THOUSANDTHS





Bob
 
I beleive your time SEQUENCE must also be set to HH:MM:SS.SSS for this to work properly!
 
David Blocker
[EMAIL PROTECTED]
781-784-1919
Fax: 781-784-1860
Cell: 339-206-0261

----- Original Message -----
From: [EMAIL PROTECTED]
To: RBG7-L Mailing List
Sent: Friday, December 31, 2004 9:54 AM
Subject: [RBG7-L] - TIME IN THOUSANDTHS


Can someone either duplicate this or tell me what I am doing wrong?


I have a ENTRY form, single table

In that table, the first column is called CODEX, with a time datatype.


On before start EEP I have

Set time format HH:MM:SS.SSS

SET VARIABLE VCODEX = .#TIME

In the fom I have a variable CODEX = .VCODEX (where codex is my indexed unique identifier column)

From the R:prompt, I can see my variable like this 08:22:33.014, showing all minutes, seconds and thousandths.

When the form row is saved the thousandths only appear as 000.

Is this a bug or am i doing something wrong?


TIA., Bob C.

Reply via email to