A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Combo Box AfterUpdate Help



 
 
Thread Tools Display Modes
  #21  
Old January 7th, 2006, 04:22 PM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default Combo Box AfterUpdate Help

My criticisms are only of the _possible_ shortcomings of your relational
database design, I see no need to make personal attacks, nor have I made
any.

You should reflect on your reaction to this criticism.

I think you should apologise to TC, I do not know this poster nor do I feel
he has given rise to your objectionable remarks.

Personally I can live with your opinion of me, even if that view is based
merely on my criticism of the _possible_ shortcomings of your relational
database design.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

"Harry Thomas" wrote in message
...
Duane

Like I said before, I am not normally rude but what do you expect. He is
allowed to make rude remarks towards me and then make fun of the fact and
nothing is said. I call him a pompous arse and suggest his mate TC might
need
breathing apparatus and the whole world is up in arms against me.

Sorry, I know I shouldn't add fuel to the fire but they deserve it.

"Duane Hookom" wrote:

You are rapidly losing any support you might have gotten as you continue
throwing fuel on the fire.

Why can't people just take responsibility for their comments? When it's
appropriate, we can criticize solutions, methods, designs,.. but it is
rarely acceptable to direct criticism toward a person.

--
Duane Hookom
MS Access MVP
--

"Harry Thomas" wrote in message
...
Duane
Thank you for yor support, its a shame that Morrison now finds it so
amusing. I am not normally rude and I appreciate your comments. Its
just a
shame that I came across that pompous arse and his mate TC, whose head
is
so
far up Morrison''s arse he must be short of air.

"Duane Hookom" wrote:

Craig,
I think one of the issues was your lack of bed-side manner by using
the
phrase "help you make an arse out of your database" and then later
"big
buckets of merde". I expect you can understand how if someone has
really
worked hard on a project that being presented with a critique using
these
phrases might be a little extreme. What might seem harmless to us is
perceived as offensive by others.

I am often very short (and possible seem curt/rude) with my responses.
I
try
to not be too judgmental but it's often difficult to hide my opinions.
You
will find this true with almost every person who attempts to help here
on
a
regular basis. I recall a recent thread where the very wise and kind
John
Vinson was perceived as rude by an OP. He immediately apologized
changed
the
course of his response. He took responsibility for the perception of
another
person. It would be ideal if everyone showed the same demeanor.

--
Duane Hookom
MS Access MVP
--


"Craig Alexander Morrison" wrote
in
message ...
Let's remind ourselves of your original question in the earlier
thread:

"I have two tables in an ordering system database. One contains
names,
phone numbers etc of staff placing the orders and the other the main
table
containing full details of the order. I use a combo box in a form to
select the name of the staff member from the staff table and place
this
name in the main table. How do I also get other data to transfer
across
at
the same time, ie place the phone number from the staff table into a
corresponding field in the main table."

Now to many he placing the Staff Member's Name and Phone Number
in
the
Order table having copied them from the Staff table would appear to
be
not
in compliance with the rules of normalisation. This Staff and Order
data
could be made available in reports and forms using queries to
collate
the
data.

The slanging match as you put it would appear to be one sided I have
only
pointed out the likely failings in your database design, whereas you
have
decided to suggest that I may be an arse (not without the bounds of
possibility (vbg)) for being hesitant about your design.

Whilst I did provide some guidance on how to acheive what you wanted
to
achieve I felt it was my responsibility to point out that you may
have
taken a wrong turn.

Others use these newsgroups and read the messages that they have not
contributed to and glean useful information from them from time to
time.
It would be irresponsible of me to just answer your question without
being
curious as to the reason for such a requirement, someone lurking may
be
in
a similar situation and now they are thinking maybe my database
design
is
wrong, rather than just applying multiple values from a single
combo-box
and stuffing one table with duplicate data from another.

Indeed everyone who did answer your question was also curious about
your
design...see the pattern emerging?

As stated earlier in this thread, I can think of legitimate reasons,
"point-in-time" and "compound Foreign Key" however 99 times out of a
100
it is usually a badly normalised relational database design. For me
a
database design that is not fully normalised is generally insert
expletives of choice. Access really does reward your application
development if you are working on a fully normalised relational
database.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

"Harry Thomas" wrote in
message
...

Before the rest of you pick on me, I didn't start this slanging
match.
I
asked a simple question and got back a lengthy reply about database
design
together with accusations that I was making an arse out of my
design
and
that
my approach was big buckets of merde. What is even more incredible
is
that
the reply from Mr Morrison is based on assumptions made by him
about
the
design of a database of which he has no knowledge. I do not for one
minute
doubt his ability or expertise and I wouldn't be posting such
questions
if
I
knew the answer. I do not however think it fair to receive such a
reply.




--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited
"Harry Thomas" wrote in
message
...
Before the rest of you pick on me, I didn't start this slanging
match.
I
asked a simple question and got back a lengthy reply about database
design
together with accusations that I was making an arse out of my
design
and
that
my approach was big buckets of merde. What is even more incredible
is
that
the reply from Mr Morrison is based on assumptions made by him
about
the
design of a database of which he has no knowledge. I do not for one
minute
doubt his ability or expertise and I wouldn't be posting such
questions
if I
knew the answer. I do not however think it fair to receive such a
reply.

"Harry Thomas" wrote:

I asked a question and expected a reasonable answer, if I wanted a
lecture on
database design I would have asked for that instead. You have no
idea
of
the
design, the examples I gave yesterday and today were purely to get
an
answer
to a question. So unless you want to make an arse of yourself,
read
the
question.

"Craig Alexander Morrison" wrote:

Dodgy design as already pointed out in "Updating....." thread
yesterday.

I think you will find most people will consider your design
flawed.

Anyway use the Column property of the ComboBox as already stated
yesterday.

I am hesitant to help you make an arse out of your database
however
in
the
AfterUpdate event procedure of the ComboBox do something like
this:

Me!FieldB4 = Me!cboFieldA1.Column(1)

This assumes that cboFieldA1 is bound to FieldA1 and that
FieldA3
is
the
next column.

In this case with the correct design you would not need any code
if
the
value of FieldA1 was the primary key of the table being
referenced
and
FieldB4 was the foreign key in the related table.

I speak from 25 years of experience with Relational Databases
and
nearly 15
with Access/Jet.

I would strongly recommend you redesign your database conforming
to
the
relational model rather than the big buckets of merde approach.

This last sentence is the one that is of most help to you
although
you
may
not realise it.


--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

"Harry Thomas" wrote in
message
...
I have two tables, TableA and TableB. In a form I use a combo
Box
to
select
data from Field1 in TableA and place it in Field2 in TableB.
What
is
the
exact command I put in the AfterUpdate field of the combo box
to
also take
data from Field3 of TableA and place it in Field4 of TableB.

Thank you
















  #22  
Old January 9th, 2006, 12:16 AM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default Combo Box AfterUpdate Help


Craig Alexander Morrison wrote:

I think you should apologise to TC, I do not know this poster nor do I feel
he has given rise to your objectionable remarks.


Apparently you & I are a menage a deux! And I don't even know you!!

TC [MVP Access]

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Hidden Power of the Combo Box JethroUK© New Users 2 October 24th, 2005 09:18 AM
Show controls when value is selected in combo box jped Using Forms 12 August 23rd, 2005 11:35 PM
Combo used for Find does not trigger AfterUpdate Event Pat Garard General Discussion 3 June 14th, 2005 06:43 AM
Display column 4 in combo box AfterUpdate Bradley C. Hammerstrom New Users 2 May 27th, 2004 06:29 PM
Requery Combobox MJ Running & Setting Up Queries 7 May 25th, 2004 11:01 AM


All times are GMT +1. The time now is 05:16 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.