[AccessD] Checking for "holes" in a sequence using SQL

Understood.
Is it bad for to store the actual data, when using text, if they all share
the same prefix?

-----Original Message-----
From: Stuart McLachlan [mailto:stuart at lexacorp.com.pg]
Sent: Thursday, November 04, 2004 6:05 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Checking for "holes" in a sequence using SQL

On 4 Nov 2004 at 14:27, Joe Rojas wrote:

> Arthur,
>
> I was not expecting the database to act intelligently. To be honest I was
> not expecting there to even be a solution to this although Gustav figured
it
> out!
>
> I have an Access database that I used to keep track of the computers at my
> company. The computer naming convention that I use is TNCO###. One of the
> fields in the table is used for storing the computer name. If I remove a
> computer from our network and physical remove it from the company, I would
> like to be able to reuse that computer name instead of just using the next
> sequential number. To me I do not see it as concatenating two column
values
> into one but I could be wrong. What do you think Arthur?
>

If you *always* use the same initial characters, you could just store the
numeric value in the table and display them formatted as "TNCO"000 

--
Stuart


--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



This electronic transmission is strictly confidential to TNCO, Inc. and
intended solely for the addressee. It may contain information which is
covered by legal, professional, or other privileges. If you are not the
intended addressee, or someone authorized by the intended addressee to
receive transmissions on behalf of the addressee, you must not retain,
disclose in any form, copy, or take any action in reliance on this
transmission. If you have received this transmission in error, please notify
the sender as soon as possible and destroy this message. While TNCO, Inc.
uses virus protection, the recipient should check this email and any
attachments for the presence of viruses. TNCO, Inc. accepts no liability for
any damage caused by any virus transmitted by this email.