ActiveX Control

[dBNovice]

Hello all,

i will definitely appreciate any help I can get on this.... I have a
db that has 3 tables and 3 respective forms: task, subtask and
element. Subtask is a subform of task. Element is a subform of
subtask. Each form overlaps the other. You can call the other 2
forms from within the current form. The problem I am experiencing is
that whenever I add the MS DTPicker on the Task form it shows up on
the other two form. Also when I add the DTPicker on the Subtask form,
it shows up on the Element form. I have not been able to figure this
out. I tried experimenting with other controls and found that not all
the controls behave like this. The commonly used ones like text box,
command button, etc... does not "seep through" onto the other forms;
however, some of the other more advance controls do. Please I would
appreciate any insight you can give me to get a resolution to this
problem.

[storrboy]

ActiveX controls that are not packaged with Access are known for have
a variety of incompatabilites. Many of them are due to the fact that
they rely on properties that Access does not readily expose, or does
so in a different way. Whenever possible try to avoid them, and when
it's not, test the hell out of them.

As far as the Date picker goes, there have been numerous links and
code snippets posted in the past for custom calendars and date
pickers. I would suggest looking for one of those and try to make it
suit your purposes.

[storrboy]

In my opinion...
ActiveX controls that are not packaged with Access are well known for
various incompatabilites. Sometimes these are due to Access exposing
in a different manner (or not exposing) some properties that the
control requires. When ever possible avoid using them, when it's not,
test the hell out of them.

In the case of the DTPicker, there have been numerous posts in the
past offering alternatives and even some code snippets to replace the
calendar control and the picker. Try applying one of those to fit your
needs.

[dBNovice]

On Mar 7, 7:03 pm, "storrboy" <[e-mail]:

In my opinion...
ActiveX controls that are not packaged with Access are well known for
various incompatabilites. Sometimes these are due to Access exposing
in a different manner (or not exposing) some properties that the
control requires. When ever possible avoid using them, when it's not,
test the hell out of them.

In the case of the DTPicker, there have been numerous posts in the
past offering alternatives and even some code snippets to replace the
calendar control and the picker. Try applying one of those to fit your
needs.

Thank you for responding. I thought I was doing something wrong. I
used an alternative and it worked great!

DTPicker alternative: http://www.fontstuff.com/access/acctut09.htm

[storrboy]

DTPicker alternative:http://www.fontstuff.com/access/acctut09.htm

Test the hell out of it.
Even though the Calendar control comes with Access, I have had issues
with it in the past.