Karen-

 

Another great place to use J-date  my .02   Keeps things clean and in order,  
when I want to go back in time.

 

Use encrypt!  They gave us this great tool and for a good reason!   My .02

 

 

--Put your own autochk process here. Do so or else…..

 

SET NULL -0-

SET TIME FORMAT hhmmss

 

-- Why var vul_ ?  VUnLoad (the 'U'=un & 'L'=load) just these incase for 
clearing var!

SET VAR vul_time = (CTXT(.#TIME))

SET VAR vul_jdate = (CTXT(JDATE(.#DATE)))

SET VAR vul_pass TEXT = 'RBaseRocks'

SET VAR vul_unique TEXT  = ('MyDBI' + (.vul_jdate + .vul_time))

SET VAR vul_out TEXT = (.vul_unique + '.all')

OUTPUT .vul_out encrypt .vul_pass

UNLOAD ALL

OUTPUT SCREEN

DISCONNECT

SET VAR vul_db1 TEXT = ('Rename MyDB.RB?  ' + .vul_unique + '.RB?')

&vul_db1

SET VAR vul_db2 TEXT = ('Run ' + .vul_out + ' ' + .vul_pass)

&vul_db2

SET TIME FORMAT HH:MM:ss.sss

CLEAR VAR vul_%

PAUSE  FOR 5 USING 'Rebuild is Complete - Now going to Re-Index !' CAPTION 
'Rebuild status' ICON confirm BUTTON 'Ok!'

disconnect

set multi off

conn MyDB

Pack all

disconnect

Set Multi on

connect MyDB

 

--Clean up what files you want

return

 

 

Sincerely,

Paul 

 

I bet my code is wrong somewhere.  I will take no offense to corrections -  
just please let me know.

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Friday, July 10, 2009 12:45 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Large integer values in Rbase v8

 

At one of my clients I use JDate as the invoice# along with the client code.   
This way I can keep it as integer.   And if you want to search invoice# by a 
date, you can prompt for the date, convert it to JDate, append the client code 
(I put the JDate first) and determine the invoice#

Karen





Hello Jan –

What if you used jdate instead?  Then you only have yyjjj.   Also unless your 
rec’v go beyond 9+ years you could just use the last digit of year.  However 
caution for this upcoming year.  Perhaps invoice number first then date id.

  

Sincerely,

Paul D

  



 

Reply via email to