RE: 10 Char object names was... -- MIDRANGE-L

× 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.

JDBC sees the long procedure names. It doesn't make a whole lot of sense that ODBC wouldn't. You can
use underscores between words if you don't like camelcase.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve
Richter
Sent: Monday, February 25, 2008 2:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: 10 Char object names was...

On Mon, Feb 25, 2008 at 1:56 PM, <rob@xxxxxxxxx> wrote:

What is really odd is that a stored procedure doesn't even physically
reside in a library. It's not as if you can do a
WRKOBJ MYLIB/*ALL *STRPRC
iNav has a way of seeing them via the database option but I am sure that
all it is displaying you is the contents of
QSYS2/SYSPROCS
And, when I query that I'll be danged if I can see any space for 10
character object names.

So, in this case, is it not the 10 character limitation, but the fact that
you use spaces, slashes and other special characters? Would using camel
case, or some such thing, be acceptable for your Crystal names?

I'll try it, thanks.

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.