Contingent formatting

[dmieluk]

Problem:

When moving between records, I need to control which combo/text boxes
are displayed on the current form, dependent upon data in the current
record.

More:

I building my first access database.

Record entry is by a single form, and the form contains many cases of
contingent combo boxes, text boxes, etc.

When building the form, I was testing only the form by itself for a
single record, not moving between records. Everything works fine so
long as you do not move between records.

However, when I move between records, the formatting (ie. which
combo/text boxes are visible/enabled) remains as it was on the most
recent manually entered record.

A simple way to address this would be to have an 'OnChangeRecord ' type
event which detects presses on the MS Access default record controls
which appear at the bottom left of the screen. Is this possible? If so,
how?

For my form formatting, I have used the _Change event for combo boxes.
Where should this formatting go, and where does it need to be to update
correctly whenever a user moves between records?

I have experimented with the Form_AfterUpdat e event without success.
Any help greatly appreciated.

[Wayne Gillespie]

On Wed, 21 Dec 2005 11:57:55 +0800, "Allen Browne" <Al*********@Se eSig.Invalid> wrote:

I would suggest that this more likely due to the [Event Procedure] not being set in the form's properties, rather than
corruption. The OP indicated that the Form_Current procedure was created directly in the VBE, which will not
automatically set the property.

Presumably this is a bound form, because the built-in nav buttons would not
do anything in an unbound form.

If Form_Current is not firing, the database is partially corrupt. Follow
this sequence until you start seeing the debug.print working.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\m saccess.exe" /decompile
"c:\MyPath\MyDa tabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

Wayne Gillespie
Gosford NSW Australia

[Allen Browne]

Good thought. Thanks Wayne and Tom. Very likely.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Wayne Gillespie" <be*****@NOhotm ailSPAM.com.au> wrote in message
news:1f******** *************** *********@4ax.c om...

On Wed, 21 Dec 2005 11:57:55 +0800, "Allen Browne"
<Al*********@Se eSig.Invalid> wrote:

I would suggest that this more likely due to the [Event Procedure] not
being set in the form's properties, rather than
corruption. The OP indicated that the Form_Current procedure was created
directly in the VBE, which will not
automatically set the property.

[dmieluk]

Ok, thank you very much guys, for all your help.

I did not have the event procedure option selected.

I have made this alteration and it has solved the problem.

Kudos to the support gurus who help out at this forum.