I didn't know Null could be set on or off. Do you mean Zero? I tried with
Zero on and off.I also tried with a null character.Patti
From: "[email protected]" <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Tuesday, November 25, 2014 1:03 PM
Subject: [RBASE-L] - Re: problems with Update command
Any change in your NULL setting? i.e. SETNULL ON/OFF?
Mike Ramsour
AK Steel Coshocton Works
Quality Department
Phone: 740-829-4340
Cell: 740-502-1659
From: Patti Jakusz <[email protected]>
To: [email protected] (RBASE-LMailing List),
Date: 11/25/2014 12:58 PM
Subject: [RBASE-L] -Re: problems with Update command
Sent by: [email protected]
Funny, I thought you had to list the tableyou were getting the data from first.
No, it didn't make a difference. Icopied and pasted your syntax. It still
worked if I took off thelast clause.
I may have to send the data to John but Ihave to change all the names and SSNs.
From: "[email protected]"<[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Tuesday, November 25, 2014 11:55 AM
Subject: [RBASE-L] - Re: problems with Update command
Patti:
>From my personal experience I would rearrange the sequence of the tablesin
>your command.
You could try this:
UPDATE actde SET casenum=T2.casenum FROM actde T1, caseid T2 WHERE
T1.ssnum=T2.ssnumAND T1.momdob=T2.momdob and T1.casenum is null
Might be worth a try.
Good luck.
Mike Ramsour
AK Steel Coshocton Works
Quality Department
Phone: 740-829-4340
Cell: 740-502-1659
From: PattiJakusz <[email protected]>
To: [email protected](RBASE-L Mailing List),
Date: 11/25/201411:52 AM
Subject: [RBASE-L]- problems with Update command
Sent by: [email protected]
I have a command file that I've been using for years. One of thesteps is, if
the Casenum field is null in the table named "actde",I populate it with data
from another table, named "caseid." I make sure the SS# and DOB are the same.
Here is my command:
UPDATE actde SET casenum=T1.casenum FROM caseid T1, actde T2 WHERE
T1.ssnum=T2.ssnumAND T1.momdob=T2.momdob and T2.casenum is null
We updated versions recently and now this command doesn't work and it
doesn'tgive me an error message. It takes me out of the application andsends
me back to the Rbase Database Explorer screen.
If I take off the last clause "t2.casenum is null", it will work.
If I reset the field back to null and select all that are null, it
acknowledgesthem.
If I add a different clause instead of T2.casenum is null, sometimes itworks
and sometimes it doesn't.
The following did not work. I tried to just update based on the nameof the
person adding the records to the table:
UPDATE actde SET casenum=T1.casenum FROM caseid T1, actde T2 WHERE
T1.ssnum=T2.ssnumAND T1.momdob=T2.momdob and T2.nameuser=.vuser
Then just to experiment, I tried a completely different field -- somethingthat
I would not logically use to complete my command file, but just fortesting, and
it worked.
It doesn't make sense why sometimes it works and sometimes it doesn't. No
typos. Like I said, I've used this command file for manyyears.
I have messages and error messages set on. I've tried with zero onand off. I
tried packing the database and it still doesn't work. I have version
9.5.2.11227.
This scares me as I use this sort of command frequently, especially
whencreating temp files for printing reports.
Confidentiality Notice
This message is intended exclusively for the individual or entity to whichit is
addressed and may contain privileged, proprietary, or otherwise
privateinformation.
If you are not the named addressee, you are not authorized to read,
print,retain, copy or disseminate this message or any part of it. If you
havereceived this message in error, please notify the sender immediately
bye-mail and delete all copies of the message.
Confidentiality Notice
This message is intended exclusively for the individual or entity to which it
is addressed and may contain privileged, proprietary, or otherwise private
information.
If you are not the named addressee, you are not authorized to read, print,
retain, copy or disseminate this message or any part of it. If you have
received this message in error, please notify the sender immediately by e-mail
and delete all copies of the message.
