Re: Combo Box AfterUpdate Help

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" <HarryThomas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:1A035E32-DF85-442B-8D24-9EA87A84E34A@xxxxxxxxxxxxxxxx
> > >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
> >
> >
> >
> >
> >
.

Relevant Pages

  • Re: Dynamic column specification in table update
    ... Pro SQL Server 2000 Database Design - ... > primary key should be made up from your data. ... >> The only excuses tend to fall along the lines of laziness or ignorance. ...
    (microsoft.public.sqlserver.programming)
  • Re: Key Violations in Append Queries
    ... Normally, if a primary key or other unique index is created, it is ... the design of the database requires uniqueness for the key involved. ... Whoever designed the database supposedly felt this was necessary. ... It may be that you should just omit this from the append query, ...
    (microsoft.public.access.queries)
  • Re: M:M/Multiple Keys
    ... the SyncService - you'll see that things like the value of a primary key is ... keys is that while your design become deeper and deeper, ... database itself but in the interface as well. ... I stopped using composite keys many years ago and since then, ...
    (microsoft.public.access.modulesdaovba)
  • C# programmer looking for a job
    ... Software Development including Desktop, Client/Server and Database ... Practical skills in object oriented design and design patterns ... XML, Oracle, CVS, VSS, Delphi, bug tracking. ... Developed in Delphi5; ...
    (misc.immigration.usa)
  • Re: Key Violations in Append Queries
    ... Normally, if a primary key or other unique index is created, it is because ... the design of the database requires uniqueness for the key involved. ... Whoever designed the database supposedly felt this was necessary. ...
    (microsoft.public.access.queries)