E
Elvis
Hello,
I am using Access 2000 (my company doesn't believe in upgrades
) and
using Oracle as a back-end. I have a form with a subform representing a
master detail relationship where
Attribute table
attrib_id, Name, Mandatory, default_
AttributeValues table
attribval_id, attrib_id, Value_
These are referenced by a projects table. I won't get into those tables.
For attributes which are mandatory I need to allow the user to assign a
default. The way I have done this on the form is to place a unbound radio
button on each record of subform. Then place a transparent button over top of
the radio button so the user can toggle it. The radio button references the
default_ field in the parent to decide if it is on or off.
When a user changes a non-mandatory attribute to mandatory the default must
be assigned to each project which doesn't not already have that attribute.
In my previous Access-Access solution (using split access database) when
user changed attribute to mandatory the user could change the default and
save the form and at that point in the afterupdate event I could apply the
attributes. But in the Oracle solution using Oracle ODBC driver. when the
user changes to mandatory and then clicks on the subform the afterupdate is
executed and the wrong default is applied. My only solution is to ask the
user, add a button which performs this operation separately.
Any ideas if this is just how it is with ODBC and Oracle, will moving to
Access 2003 allow me to resolve this, or have I done something wrong - am I
dreaming this?
Any help appreciated.
Thanks.
Elvis
I am using Access 2000 (my company doesn't believe in upgrades
) andusing Oracle as a back-end. I have a form with a subform representing a
master detail relationship where
Attribute table
attrib_id, Name, Mandatory, default_
AttributeValues table
attribval_id, attrib_id, Value_
These are referenced by a projects table. I won't get into those tables.
For attributes which are mandatory I need to allow the user to assign a
default. The way I have done this on the form is to place a unbound radio
button on each record of subform. Then place a transparent button over top of
the radio button so the user can toggle it. The radio button references the
default_ field in the parent to decide if it is on or off.
When a user changes a non-mandatory attribute to mandatory the default must
be assigned to each project which doesn't not already have that attribute.
In my previous Access-Access solution (using split access database) when
user changed attribute to mandatory the user could change the default and
save the form and at that point in the afterupdate event I could apply the
attributes. But in the Oracle solution using Oracle ODBC driver. when the
user changes to mandatory and then clicks on the subform the afterupdate is
executed and the wrong default is applied. My only solution is to ask the
user, add a button which performs this operation separately.
Any ideas if this is just how it is with ODBC and Oracle, will moving to
Access 2003 allow me to resolve this, or have I done something wrong - am I
dreaming this?
Any help appreciated.
Thanks.
Elvis