Hi all. I recently upgraded from Access 2003 to Access 2007 and I've run into an odd problem with the Command Button wizard. I know that the Command Button wizard defaults to creating embedded macros instead of event procedures, even if the option is set to always use event procedures, but that isn't the problem.
The Problem: I want to use the command button wizard to create a button that opens a form and finds specific data to display (a routine function), but when I get to the point in the wizard where it asks me to specify which fields contain the matching data, the right side pane is populated properly with the fields from the table containing the foreign key (tblExpenses), but the left side pane which is supposed to be populated with all the fields from the table which contains the primary key (tblPlaces) is completely empty, so it isn't possible to actually select the fields with the matching data and go on to finish the wizard.
Workaround: I've already solved this problem by abandoning the stupid wizard and writing the VBA code myself to get the job done (the same code generated by the wizard in Access 2003), so the button is already working as it should. But I still have no idea why the left side pane in the button wizard didn't show any fields as it should have.
I searched this and found where another user asked about the exact same problem. The advice there was to use VBA instead of the wizard, but again - that advice doesn't explain why the left side pane in the wizard was empty. My forms are bound to the underlying tables, so the problem is not being caused by the use of unbound fields. The fact that routine VBA code solved the problem, and the fact that the subdatasheet in the primary table shows the correct filtered data in the related table both prove that the tables and relationships are set up and functioning properly. Also, I've long since been to the Trust Center and done the necessaries there, including subfolders.
So, does anyone here know why the left side pane in the command button wizard would be empty rather than showing a list of fields as it should? I like a good brain teaser, but I'm getting a headache. Hopefully I've supplied all the needed information for someone to be able to recognize the problem and answer this.