×
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.
I ran into a situation where I was getting a pointer error on a file
read which was making me go 'huh?'
Near as I can tell, the issue happened because a file field name had the
same name as a procedure's parameter in the service program.
So if a file has a field named Order#. And a procedure has a field
named Order# (and it happened to be a difference procedure than the one
reading the file). Then the read was resulting in a pointer error
(because obviously Order# from the other procedure is not in memory).
To fix the issue I changed the read to drop the data in a local data
structure.
Just thought I'd throw this out there so others are aware of this
not-classic-at-all trap (or is it classic and I just didn't know?)
Kurt Anderson
Application Developer
Highsmith Inc.
W5527 State Road 106, P.O. Box 800
Fort Atkinson, WI 53538-0800
TEL (920) 563-9571 FAX (920) 563-7395
EMAIL kjanderson@xxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
