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 wouldrearrange the sequence of the tables in
>your command.
You could try this:
UPDATE actde SET casenum=T2.casenum FROMactde T1, caseid T2 WHERE
T1.ssnum=T2.ssnum AND T1.momdob=T2.momdoband 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-LMailing 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 usingfor years. One of the steps is, if
the Casenum field is null in thetable named "actde", I populate it with data
from another table,named "caseid." I make sure the SS# and DOB are thesame.
Here is my command:
UPDATE actde SET casenum=T1.casenum FROMcaseid T1, actde T2 WHERE
T1.ssnum=T2.ssnum AND T1.momdob=T2.momdoband T2.casenum is null
We updated versions recently and now thiscommand doesn't work and it doesn't
give me an error message. Ittakes me out of the application and sends me back
to the Rbase DatabaseExplorer screen.
If I take off the last clause "t2.casenumis null", it will work.
If I reset the field back to null and selectall that are null, it acknowledges
them.
If I add a different clause instead of T2.casenumis null, sometimes it works
and sometimes it doesn't.
The following did not work. I triedto just update based on the name of the
person adding the records to thetable:
UPDATE actde SET casenum=T1.casenum FROMcaseid T1, actde T2 WHERE
T1.ssnum=T2.ssnum AND T1.momdob=T2.momdoband T2.nameuser=.vuser
Then just to experiment, I tried a completelydifferent field -- something that
I would not logically use to completemy command file, but just for testing, and
it worked.
It doesn't make sense why sometimes it worksand sometimes it doesn't. No
typos. Like I said, I've usedthis 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 databaseand it still doesn't work. I have version
9.5.2.11227.
This scares me as I use this sort of commandfrequently, 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.
