Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access2000 inconsistencies in default values of Form controls

Status
Not open for further replies.

breslj

Programmer
Jul 1, 1999
5
US
Forgive me, please, but I posted this problem on Access Forms Forum on Nov 16 and have not yet received a response. Perhaps it needs wider exposure on the General Access Forum.

In Access2000 I am having trouble consistently getting the current value of a control on a parent form to become the default value of a control on a child form.

The forms are synchronized by means of the Command Button Wizard. Once that works, I click on the desired control on the child form and then the default value line in the proper control's Properties Dialog Box. I use the Expression Builder to write the expression using the syntax [Forms]![Parent Form Name]![Parent Form Control Name].

In some cases the appropriate value appears in the child-form control, but occasionally "error" shows up or, more often, the child control is blank. In all instances there are data displayed in the parent control.

An example: the expression =[Forms]![Pre-Award, Awarded, Awarded-closed]![GNUM] results in the correct grant number being filled-in on the child form in the GNUM control. BUT =[Forms]![Pre-Award, Awarded, Awarded-closed]![DESCRIPTIO] does not produce the grant description. On one child form it is blank, but on another "error" appears.

My client does not have a resident Access developer and desires all automatic operations to be produced by expressions or wizards rather than by VBA coding.

Please help me if you can.

Jerry
Jerome Breslaw
Springfield, VA, USA

 
First of all I don't recommend setting up your db in this manner. I also strongly recommend you do not use ','s in your object names.

Anyway, have you checked to make sure that the controls (and their underlying fields) have the same (or at least compatible) datatypes? If you're tyring to plug text into a numeric field it can cause this type of problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top