Jim,

 

If the scanner is set to add a carriage return then you could put in the ON 
field exit eep;

 

set v vFormMode='Enter'  and then your code below.

 

Then you would be sure to eliminate user error and have all the code execute.

 

Also, what Karen says rings true in that if you have an insert command with 
many columns make sure you have on each line of the insert a comma and plus for 
continuation characters.

Run Rstyle through your code before saving. That will spare you a lot of 
headaches.

 

One last thing, do you need a second SAVEROW before the Insert(table 2) line ?

 

Hope this helps.

 

Bill

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
Jim Belisle
Sent: Thursday, February 27, 2020 4:30 PM
To: [email protected]
Subject: RE: [RBASE-L] - TWO INSERTS

 

Thanks Bill. That may be a help. 

 

But still it does not make sense that one table would be populated and not the 
second one. 

This is an entry code so if the code does not fire at all, neither table would 
populate. That is what confuses me. 

Why would one table populate and the other not when the second table code is 
the very next line after the first table code? No code between.

 

Code is as follows

IF vformode = 'ENTER' THEN  

 (check for proper info)

  SAVEROW

  INSERT (table 1)

 INSERT (table 2)

ENDIF

DROP temp tables

CLOSEWINDOW

 

Plus it is inconsistent. Different employees have this happen at different 
times. 

Sometimes the employee will scan into and out of many jobs during the day with 
no problem then this happens. 

Maybe I have a bad ethernet cable?? 

It might be as simple as that.

 

James Belisle

 

Making Information Systems People Friendly Since 1990

cid:[email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
Bill Eyring
Sent: Thursday, February 27, 2020 2:50 PM
To: [email protected]
Subject: RE: [RBASE-L] - TWO INSERTS

 

Jim

 

Just a thought. If the user doesn't hit the [ENTER] key will the form close ?

 

I have a client that does a lot of scanning into forms with no issues. The 
scanner is programmed to issue a carriage return after the scan. You may want 
to check the scanner settings and make sure it does a carriage return after 
scanning. Doing it that way, the users does NOT have to hit the [ENTER] key 
after scanning.

 

Hope that helps.

 

Bill Eyring

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
Jim Belisle
Sent: Thursday, February 27, 2020 3:24 PM
To: [email protected]
Subject: [RBASE-L] - TWO INSERTS

 

I have a few places in my code where I do two inserts into two different tables 
one right after the other.

Most of the time that is not a problem. 

However there is code that runs on the thin clients out in the shop (hardwire) 
where recently the second table does not get populated as it should.

Once again this is only once in awhile. 

The code runs in an on exit (from a field) EEP.

The information going into both tables is from a view.

 

First insert

  INSERT INTO inventry +

  (list of columns) +

  SELECT list of columns +

  FROM twkinvtbl

 

Second insert

 

  INSERT INTO workdetail +

  (list of columns) +

  SELECT list of columns +

  FROM twkinvtbl

 

He form closes after dropping the temp view. 

Any BLUES CLUES? 

 

(Also this field is populated by scanning a location. All they user is supposed 
to do after the scan is hit the enter key.)

 

James Belisle

 

Making Information Systems People Friendly Since 1990

cid:[email protected]

 

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbase-l/CH2PR02MB704775C028C7BDA1866388B6A0EB0%40CH2PR02MB7047.namprd02.prod.outlook.com
 
<https://groups.google.com/d/msgid/rbase-l/CH2PR02MB704775C028C7BDA1866388B6A0EB0%40CH2PR02MB7047.namprd02.prod.outlook.com?utm_medium=email&utm_source=footer>
 .

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbase-l/CH2PR02MB704713D784D501FC8A05F8BBA0EB0%40CH2PR02MB7047.namprd02.prod.outlook.com
 
<https://groups.google.com/d/msgid/rbase-l/CH2PR02MB704713D784D501FC8A05F8BBA0EB0%40CH2PR02MB7047.namprd02.prod.outlook.com?utm_medium=email&utm_source=footer>
 .

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbase-l/005401d5edbd%241a891150%244f9b33f0%24%40com.

Reply via email to