Jennifer,

I've used a basic Keyword/Variable Lookup List straight out of SAT. User
views the list for name and some basic info. IF name is not there, they
hit an ADD button which uses an 'Enter Using' form to add the name and
assign an ID#. Exiting goes immediately back to the Var Lookup List
which now has the name after a refresh. User now picks EDIT and the
'Edit Using" form pops up for more info. Previous methods had several
people add the same person twice with different ID#s without knowing
what others were doing. This 'Keyword' method at least puts a fresh name
list in front of users who need it. We are far from high volume, but do
have multiple users adding names. 

 

Tom Frederick

Elm City Center

1314 W Walnut

Jacksonville, IL 62650

O - 217-245-9504

F- 217-245-2350

Email - [email protected]

 

________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of Roberts,
Jennifer
Sent: Wednesday, December 23, 2009 2:48 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Temporary Tables Question

 

Hello,

 

I am working with version 7.6, build 7.6.8.31102 - and I am wanting to
change the way the users currently add/edit information in this
multi-user database.  I would like to have the users working in
temporary tables which would then update the permanent tables.  Could
someone kindly give some advice on how they have handled primary keys in
this situation.  For example, the user wants to enter a new client.  The
client table has a primary key that is an auto-number.  Is it better to
grab the next number from the permanent table and reserve it or generate
the key in the temporary table and then check to see if it used?  Or is
there another way that I hadn't thought of (most likely  :-)).  

 

Thank you in advance and Happy Holidays!

 

Jennifer Roberts

Business Applications Specialist

Ohio Masonic Home

Phone:  937.525.3080

Fax:  937.505.4009

Ext:  5788

 

This electronic message contains information 
from the Ohio Masonic Home,
its operating subsidaiaries or affiliates. 
The information may be 
confidential, privileged or otherwise 
protected from disclosure. 
The information is intended to be received 
solely by [email protected], 
for use as designated in the message. If you are not
the designated recipient, you are instructed not to review, 
disclose, copy, distribute orotherwise use of 
this transmission
 or its contents. If you have received this 
transmission in error, please notify the 
Ohio Masonic Home immediately
at [email protected]; in addition, 
please delete your record of 
transmission. Sending, receiving, downloading, displaying,
 printing material that is harassing, fraudulent, offensive, 
intimidating, defamatory, or otherwise
unlawful or inappropriate is strictly prohibited by The Ohio Masonic
Home.

Reply via email to