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



We have a similar situation in some of our Client/Server programs. What we
do is to place the User ID as the first key field of our table. Before we
write the data to the work file we delete all the records pertaining to the
requesting User. The client program "knows" it must read all the records
beginning with the User ID.

HTH,

Luis

On Wed, Nov 2, 2016 at 10:34 AM Roche, Bob <broche@xxxxxxxxxxxxxxxxx> wrote:

I have an interactive inventory screen. The users would like to add a few
more columns, but the 24 x 80 screen is full so I'm going with PHP.
The program to help build the inventor list uses a separate alone program
to build a work file in qtemp. The display program reads it and everything
is fine. Many people can use it at the same time since the work file is in
temporary storage. I would like to use this program but a call from PHP
can't rely on temporary storage for the next SQL call to get the data. Has
anyone already solved a similar issue, or should i just rewrite the work
file program in PHP?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--

Luis Rodriguez

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.