Al
Yes you understand what i have. But i need this code to report to
another
organisation. This is what they want. If it was up to me i would
scrap
it
but they have implented this code Australia Wide and all organisation
have
to
follow the standards.
Please can you help with the code.
Thanks
:
Andrew,
If I understand you so far...
Your autonumber key field for each Client should be all you need to
uniquely identify ANY Client, in ANY query, form, or report, so I
can't
understand why your using this very complicated string manipulation
technique to develop another "UniqueID" (along with birthdate?), to
try
to
accomplish the same thing.
You wrote...
This is an extra field i require and it doesnt matter if there
happens to be a double up in the code cause when i do the reporting
i
also
take the clients Date of Birth which 99% of the time will different.
To be honest Andrew, and saying this as kindly as I can, I think this
is
poor design, for the reasons I've given. I'm going to respectfully
back
off
on this one.
It appears as though you're attempting, through very complicated
string
manipulation, and a birthdate, to achieve some higher degree of
uniqueness
(your 99%) to identify your records, when the key field you already
have
is
100% unique.
I think that most "responders" on this newsgroup would feel the same
way,
or
at least... want to you to make a much better case as to why you want
to
do
this.
Please... feel free to create a "new" post with this issue. Other
folks
may
think this thread has played out, and you won't get any more
responses.
A
new post is the best bet.
--
hth
Al Camp
Hi Al
My mistake with Mr John Smith.
I do have an autonumber in the client table and this is how i link
my
tables. This is an extra field i require and it doesnt matter if
there
happens to be a double up in the code cause when i do the reporting
i
also
take the clients Date of Birth which 99% of the time will different.
I need this field to be included in a report to another department
and
this
is what they ask for. Other than that there will be no other use for
it
So can you advise on how to do it and whether it needs to be done on
the
table design or form design.
Thanks
:
Andrew,
What happens when you have 2 John Smiths? That's not unusual at
all.
You may not have that now, but database design has to take into
account
what
might occur in the future, and this plan will run into serious
problems
somewhere down the road.
Your ID scheme is not unique enough to rely on for database
integrity.
How do you get the ID value? Does the user enter it by hand?
If so, you made a mistake on John Smith.
John Smith - mitoh
"mit" is the 2nd 3rd and 4th character of Smith... not 2nd 3rd
and
5th
("mih")
I suggest using an Autonumber field to develop the unique IDs.
That's
what it's there for.
That field will be designed into your Client table. And...
since
it
is
used by only you to link tables, or find records, you can show it
(no
editing allowed) on a form or report... if so desired. But, not
showing
it
all to the user is the preferred method.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions
Hi
I Have a field in my Client table that i want to be a unique code
(required
for reporting Purposes) The Unique code has to be the 2nd,3rd
and
5ht
letter
of the surname and 2nd, 3rd letter of their first name. If there
is
no
character there it has to be replaced with a number 2.
Example
name Unique Id
John Smith - mitoh
Jo Day - ay2o2
Can some help and advise whether it needs to be on the Form or on
the
table
design.
Thanks