Thanks to everyone who helped me with my earlier subfile-print issue.

 

I have one quick question on my SQL code and its use.  In my subroutine,
I have:

 

          SQLstmt = 'select a.spno01, a.spno02, a.spno03, a.spptno,';

          SQLstmt = SQLstmt + ' a.spptcl, a.spoqty,';

          SQLstmt = SQLstmt + ' b.scsnm, a.sprccd, a.spsddt, a.spsdtm,';

          SQLstmt = SQLstmt + ' a.sptrmd, a.sprmrk, a.spusr, a.spscnf';

          SQLstmt = SQLstmt + ' FROM SST30 a, SSM01 b ';

          SQLstmt = SQLstmt + ' WHERE a.spplcd = ' + apos + plcd + apos;

          SQLstmt = SQLstmt + ' AND a.spsddt BETWEEN ' +
%char(SPODATEF);

          SQLstmt = SQLstmt + ' AND ' + %char(SPODATET);

          SQLstmt = SQLstmt + ' and concat(a.spspcd,a.spsplc)'

          SQLstmt = SQLstmt + ' = concat(b.sccd,b.sclc)';

 

Further in the code, I open a cursor and put the fields into it based on
this SQL code.  The code for this fetch command is:

 

     C+ FETCH spocsr

     C+ INTO :spno01, :spno02, :spno03, :spptno, :spptcl,

     C+ :spoqty, :scsnm, :sprccd, :spsddt, :spsdtm,

     C+ :sptrmd, :sprmrk, :spusr, :spscnf

 

However, when I compile the program, it balks at the :SCSNM in my fetch
statement.  This field is in the second table (SSM01), but I create a
table relationship through my WHERE x = y statement.

 

Can someone explain why it will not use the SCSNM field from the SQL
statement and how I can fix the problem?

 

Thanks!


Brian.

 

-=-=-=-=-=-=-=-=-=-=-=-=-=-

Brian Piotrowski

Specialist - I.T.

Simcoe Parts Service, Inc.

Ph: 705-435-7814 x343

Fx: 705-435-6746

bpiotrowski@xxxxxxxxxxxxxxx

-=-=-=-=-=-=-=-=-=-=-=-=-=-

 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.