Hi,
I don’t know for sure why you change your null setting to a space, but I don’t like the idea. Maybe I am terribly wrong, but this could cause unexpected results elsewhere. If for instance a field elsewhere in the database only contains a space – which is not very probable, I admit – it is translated into a null value afterwards. Tony IJntema From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: donderdag 17 maart 2011 20:03 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Data corruption Karen This the code... thanks Marc LABEL tcstart RUN fcust IN prog7.apx IF (LASTKEY(0)) = '[ESC]' THEN GOTO tcend ENDIF SET VAR vcust INTEGER = .cust# IF cust# IS NOT NULL THEN SET NULL ' ' EDIT USING t1c WHERE custnum = .cust# + ORDER BY txdate ASC CAPTION 'Travel Card' IF SQLCODE = 100 THEN SET NULL ' ' INSERT INTO travcard (custnum,txdate) VALUES (.cust#,.#DATE) EDIT USING t1c WHERE custnum = .cust# + ORDER BY txdate ASC CAPTION 'Travel Card' ENDIF SET NULL -0- GOTO tcstart ENDIF LABEL tcend From: [email protected] Sent: Thursday, March 17, 2011 1:38 PM To: RBASE-L Mailing List <mailto:[email protected]> Subject: [RBASE-L] - Re: Data corruption Marc: Since you say "they stay in a Loop", is this a While loop? Do you have whileopt set off? Nothing can chew up memory and cause problems more than having whileopt on and not followig "the programming rules". Karen I will check the Var’s, I never really thought of that since they stay in a Loop Dialog ... Custnum Edit Using Form click a few buttons, maybe type in the Varchar field Exit to the Dialog box and then do the next Custnum Worth taking a second look, but if I have to do over 10 rows to find the problem it may make it hard. Marc
