image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

Is that a question? The one on the left has a "Not Connected" status, so I would guess that file is cached on your PC, while the one on the right is loaded from your IFS.

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

Is that a question? The one on the left has a "Not Connected" status, so I would guess that file is cached on your PC, while the one on the right is loaded from your IFS.

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

Dear David

>>>> Every time I open a file it is making me connect to the IBM i...  is there a setting that causes it to retain the connection until I power off? <<<<

In the old and unsupported IBM i Access for WIndows, there is a preference setting to Prompt Every Time you connect any of its components to IBM i. I see no such setting in Access Client Solution.   Are you using Run SQL Script from this IBM i Access for Windows?    If so, you can set it to use the same connection (I do not remember the wording of the option).

Is that a question? The one on the left has a "Not Connected" status, so I would guess that file is cached on your PC, while the one on the right is loaded from your IFS.

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

Dear David

>>>> Every time I open a file it is making me connect to the IBM i...  is there a setting that causes it to retain the connection until I power off? <<<<

In the old and unsupported IBM i Access for WIndows, there is a preference setting to Prompt Every Time you connect any of its components to IBM i. I see no such setting in Access Client Solution.   Are you using Run SQL Script from this IBM i Access for Windows?    If so, you can set it to use the same connection (I do not remember the wording of the option).

Is that a question? The one on the left has a "Not Connected" status, so I would guess that file is cached on your PC, while the one on the right is loaded from your IFS.

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

Dear David

>>>>   ...... that may be how it is supposed to work <<<<

I confirm that is the way it works.  When you invoke Run SQL Script from the main GUI windows of Access Client Solution, it immediately prompts you to log on to the current system specified in ACS's main screen.   When you invoke it from outside of ACS screen (Windows' file association mechanism at work), it does not try to connect to any system until you want to do some thing with it that needs an established connection. Or you can manually start the connection from its menu bar.

Dear David

>>>> Every time I open a file it is making me connect to the IBM i...  is there a setting that causes it to retain the connection until I power off? <<<<

In the old and unsupported IBM i Access for WIndows, there is a preference setting to Prompt Every Time you connect any of its components to IBM i. I see no such setting in Access Client Solution.   Are you using Run SQL Script from this IBM i Access for Windows?    If so, you can set it to use the same connection (I do not remember the wording of the option).

Is that a question? The one on the left has a "Not Connected" status, so I would guess that file is cached on your PC, while the one on the right is loaded from your IFS.

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

------------------------------
David Strawn
------------------------------

Dear David

Another possible explanation for what you encountered is that you opened the first file from a Windows network drive that was mapped to IBM i NetServer IFS but the second file you opened from a "member" of a source physical file in DB2 library. When referring to a file in IBM i context, the word "member" has a specific meaning that other platforms do not have.  Stream file in IFS does not support this concept of file member. So, I wonder if you used this word in an exact meaning or not in your post? 

Did you take your action more than once and still see this same strange result every time?  If so, you should post the screens of your intermediate actions for each case as well. The clue for explanation may lie somewhere in these intermediate steps of your action.

------------------------------
Education is not the learning of facts but the training of the mind to think. -- Albert Einstein.
------------------------------
Satid S.
------------------------------

Original Message:
Sent: Fri March 24, 2023 03:51 PM
From: David Strawn
Subject: Run SQL Scripts from ACS for IBM i

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

------------------------------
David Strawn
------------------------------

Original Message:
Sent: 3/27/2023 2:54:00 AM
From: Satid Singkorapoom
Subject: RE: Run SQL Scripts from ACS for IBM i

Dear David

Another possible explanation for what you encountered is that you opened the first file from a Windows network drive that was mapped to IBM i NetServer IFS but the second file you opened from a "member" of a source physical file in DB2 library. When referring to a file in IBM i context, the word "member" has a specific meaning that other platforms do not have.  Stream file in IFS does not support this concept of file member. So, I wonder if you used this word in an exact meaning or not in your post? 

Did you take your action more than once and still see this same strange result every time?  If so, you should post the screens of your intermediate actions for each case as well. The clue for explanation may lie somewhere in these intermediate steps of your action.

------------------------------
Education is not the learning of facts but the training of the mind to think. -- Albert Einstein.
------------------------------
Satid S.

Original Message:
Sent: Fri March 24, 2023 03:51 PM
From: David Strawn
Subject: Run SQL Scripts from ACS for IBM i

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

------------------------------
David Strawn
------------------------------

Dear David

I'm just able to see clearly both your screen shots and it is very clear that these two ARE NOT THE SAME CODE. Please go through them line by line and you will see clear differences of the code.  The first difference I see is on line 7-9 on the right side which has one more line and different code than the left. Next difference I see is the last two lines of the right side that are different from the left side.

To me, it is likely that you opened two different source code files without your awareness.   To check on this, from Run SQL Script tool main menu, you can try looking at  File --> Recent Files that may gives you some clue on this issue.

------------------------------
Education is not the learning of facts but the training of the mind to think. -- Albert Einstein.
------------------------------
Satid S.
------------------------------

Original Message:
Sent: Mon March 27, 2023 10:38 AM
From: David Strawn
Subject: Run SQL Scripts from ACS for IBM i

Original Message:
Sent: 3/27/2023 2:54:00 AM
From: Satid Singkorapoom
Subject: RE: Run SQL Scripts from ACS for IBM i

Dear David

Another possible explanation for what you encountered is that you opened the first file from a Windows network drive that was mapped to IBM i NetServer IFS but the second file you opened from a "member" of a source physical file in DB2 library. When referring to a file in IBM i context, the word "member" has a specific meaning that other platforms do not have.  Stream file in IFS does not support this concept of file member. So, I wonder if you used this word in an exact meaning or not in your post? 

Did you take your action more than once and still see this same strange result every time?  If so, you should post the screens of your intermediate actions for each case as well. The clue for explanation may lie somewhere in these intermediate steps of your action.

------------------------------
Education is not the learning of facts but the training of the mind to think. -- Albert Einstein.
------------------------------
Satid S.

Original Message:
Sent: Fri March 24, 2023 03:51 PM
From: David Strawn
Subject: Run SQL Scripts from ACS for IBM i

image on the left is the result of double clicking on an SQL script (.sql) from the ifs.  Image on the right is when i used the open file menu option to open the exact same member, yet there are 2 different results...

------------------------------
David Strawn
------------------------------