× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Code queries
  • From: Robin Coles <robin@xxxxxxxxxxxx>
  • Date: Tue, 27 Mar 2001 16:55:34 +0100

I love Code/400. but I've got a couple of minor problems with SQL and wonder
if I've missed ways around them.... 

1) With SQLRPGLE source members, the compile errors never appear in the
error list window.

2) If I edit a SQLRPGLE program for the first time, CODE knows it's SQLRPGLE
and allows the SQL lines in the source without complaint.  Try to compile it
and it runs CRTBNDRPG instead of the CRTSQLRPGI SQL equivalent.

3) Occasionally a failed CRTSQLRPGI stops the Code host server.  I use a
session as the server and there aren't any obvious error messages.

4) I've got notify on completion selected, but on a failed create
(obviously, I don't see many of these :-) the default button is display
command window.  I can't remember ever wanting to do this.  Is there any way
to make the "No" button, or to allow Escape, or something else that's easy
to hit in frustration to kill the window?  I know I can shut confirmations
off completely,  but I just gotta know....

Are there work-arounds for these?

Cheers
Robin
+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.