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



Many years ago I went to single record control files by application.

For example, I have a billing control file with a single record that
contains:

INVMS Invoice Message 84 A
SVCLM1 Service Charge Limit #1 7,2 P
SVCAM1 Service Charge Amount #1 5,2 P
SVCLM2 Service Charge Limit #2 7,2 P
SVCAM2 Service Charge Amount #2 5,2 P
SVCLM3 Service Charge Limit #3 7,2 P
SVCAM3 Service Charge Amount #3 5,2 P
SVCLM4 Service Charge Limit #4 7,2 P
SVCAM4 Service Charge Amount #4 5,2 P
SVCLM5 Service Charge Limit #5 7,2 P
SVCAM5 Service Charge Amount #5 5,2 P
SVCCHGDS Service Charge Description 50 A
DATE1 Billing Date *ISO
LSTIN Last Invoice Number 7,0 P
DAY Billing Day 1,0 S
LSTOR Last Order Number 7,0 P
LSTCB Last Consolidated Billing 7,0 P
LSTAK Last OW Acknowledge Number 5,0 P
FSCAM Fuel Surcharge Amount 5,2 P
FSCDS Fuel Surcharge Description 50 A

Other applications like receivables, payables, etc have similar single
record control files.

I just felt better putting this stuff in a DB file instead of a data area.



On Thu, Mar 13, 2014 at 4:47 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

Contracts are added to our database by going to a dataara and retrieving
the next contract number.

This next contract number is used to add the new contract record.
(contract number is primary unique key).

It is possible that contract numbers already exist sporadically, so
somewhere in the logic the contract file must be checked for key existence.




Is it OK to find the next contract # during the contract add? I would
think that this would be risky and it may be better to simply bump the data
area by 1 and then wait and validate it is unique whenever the NEXT user
tries to add a contact.


Any suggestions?

Thanks

______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





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.