Yes, I tried sticking -0- in the as the null symbol. And if I just select all
where casenum is null, Rbase finds them all.
A few minutes ago, I aborted the program to try the first set of suggestions.
I didn't clear all my variables when we started the data-entry program back up
afterwards. I just ended the program again to try the suggestion below, but
this time the program ended normally. The update command was successful and
did what it was supposed to do.
So I guess that means a variable was defined somewhere along the line, that
needs to be defined earlier. But that doesn't make sense because there are no
variables in the command that aborted the file a few times.
I ran it again from the R> prompt,, making sure all variables were cleared
first, and it worked again. This is kind of scary. I hate it when things
don't work, sometimes.
Patti
From: Dennis McGrath <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Tuesday, November 25, 2014 1:04 PM
Subject: [RBASE-L] - Re: problems with Update command
<!--#yiv2702262260 _filtered #yiv2702262260 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv2702262260 {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;} _filtered #yiv2702262260 {font-family:Calibri;panose-1:2
15 5 2 2 2 4 3 2 4;} _filtered #yiv2702262260 {font-family:Tahoma;panose-1:2 11
6 4 3 5 4 4 2 4;}#yiv2702262260 #yiv2702262260 p.yiv2702262260MsoNormal,
#yiv2702262260 li.yiv2702262260MsoNormal, #yiv2702262260
div.yiv2702262260MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New
Roman", "serif";}#yiv2702262260 a:link, #yiv2702262260
span.yiv2702262260MsoHyperlink
{color:blue;text-decoration:underline;}#yiv2702262260 a:visited, #yiv2702262260
span.yiv2702262260MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv2702262260
p.yiv2702262260MsoAcetate, #yiv2702262260 li.yiv2702262260MsoAcetate,
#yiv2702262260 div.yiv2702262260MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma",
"sans-serif";}#yiv2702262260 span.yiv2702262260BalloonTextChar
{font-family:"Tahoma", "sans-serif";}#yiv2702262260
span.yiv2702262260EmailStyle19 {font-family:"Calibri",
"sans-serif";color:#1F497D;}#yiv2702262260 .yiv2702262260MsoChpDefault
{font-size:10.0pt;} _filtered #yiv2702262260 {margin:1.0in 1.0in 1.0in
1.0in;}#yiv2702262260 div.yiv2702262260WordSection1 {}-->Try UPDATE actde SET
casenum=T2.casenum FROM actde T1, caseid T2 +WHERE T1.casenum is null AND
T1.ssnum=T2.ssnum AND T1.momdob=T2.momdob This reduces the rows initially
retrieved from T1 and then joins to T2. Are you sure acted.casenum is really
NULL? make sure NULL is -0- and look at your data in that column.If you see
blanks, they are not really NULL
From: [email protected] [mailto:[email protected]] On Behalf Of Patti Jakusz
Sent: Tuesday, November 25, 2014 11:55 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: problems with Update command Funny, I thought you had
to list the table you were getting the data from first. No, it didn't make a
difference. I copied and pasted your syntax. It still worked if I took off
the last clause. I may have to send the data to John but I have 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 tables in
>your command.
You could try this:
UPDATE actde SET casenum=T2.casenum FROM actde T1, caseid T2 WHERE
T1.ssnum=T2.ssnum AND 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: Patti Jakusz <[email protected]>
To: [email protected] (RBASE-L Mailing List),
Date: 11/25/2014 11: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 the steps 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.ssnum AND T1.momdob=T2.momdob and T2.casenum is null
We updated versions recently and now this command doesn't work and it doesn't
give me an error message. It takes me out of the application and sends 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 acknowledges
them.
If I add a different clause instead of T2.casenum is null, sometimes it works
and sometimes it doesn't.
The following did not work. I tried to just update based on the name of the
person adding the records to the table:
UPDATE actde SET casenum=T1.casenum FROM caseid T1, actde T2 WHERE
T1.ssnum=T2.ssnum AND T1.momdob=T2.momdob and T2.nameuser=.vuser
Then just to experiment, I tried a completely different field -- something that
I would not logically use to complete my command file, but just for testing,
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 many years.
I have messages and error messages set on. I've tried with zero on and 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 when
creating temp files for printing reports.
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.
