[AccessD] Two Questions

Karen Rosenstiel karenr7 at oz.net
Mon Jun 12 20:10:58 CDT 2006


Only 1 person at a time. 


Regards,

Karen Rosenstiel
Seattle WA USA 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim
Sent: Monday, June 12, 2006 7:30 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Two Questions

If more than one person is updating the database at the same time doesn't
there need to be a variable or table that reserves the next highest number
for a user so that dmax doesn't return the same answer to two users entering
data?
Jim Hale

-----Original Message-----
From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com]
Sent: Saturday, June 10, 2006 12:15 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Two Questions


Karen:

The domain function would be I think:

lngNewIDCode=Dmax("fldDictationID","tblTableWhereTheDictationIDIs") +1

That would generate a new ID one more than the greatest current Dictation ID
number and it would end up in lngNewIDCode which you'd have to define as Dim
lngNewIDCode as Long.  

If it's a bound form where they're adding the record I'd try it in the
Before Insert event setting the DMax value to the bound field on your form
in the table where this dictation ID goes.  

Actually, what I'd do is make it a message box first and see if it's
generating the right number.

Re: the two tables - could you just put in a phone number field and a pager
field and keep it in one table??

Rocky




Karen Rosenstiel wrote:
> Hi Rocky,
> The dictation ID code is up to about 12,386 or something like that. 
> I'm
not
> at work so don't remember the exact number. So I would want to start 
> incrementing from there. What's a domain function and where do I put it?
Be
> gentle -- I'm still pretty much a newbie  ;-)
>
> The reason I wanted to break the table into 2 is because I thought 
> there might be more than 1 number, but maybe not. The other data is 
> unique, so I guess this could be too. Basically the provider has an 
> office phone and a pager that the medical center provides. So all we 
> really need is just 1 number that we could communicate to this provider
with.
>
> I guess I'll just import this table straight across and clean it up. 
> I've already set up 2 clean tables for their credentials (i.e., MD, 
> Attending; MD, Resident; Intern etc.)
>
> So thanks on the first part about incrementing.
>
>
> Regards,
>
> Karen Rosenstiel
> Seattle WA USA
>
>

***********************************************************************
The information transmitted is intended solely for the individual or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of or
taking action in reliance upon this information by persons or entities other
than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email, you are
responsible for screening its contents and the contents of any attachments
for the presence of viruses. No liability is accepted for any damages caused
by any virus transmitted by this email.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com






More information about the AccessD mailing list