Follow-up to my Access 2000 synch issue between the TaskListF and TaskF.

I could not get the macro OpenTaskM to work no matter what I tried. However, I was able to get the same failure to occur when VBA was used, and was able to correct the problem.

To Replicate the problem, I used a little VBA that replaced the Macro in the OnCurrent event. I issued:

DoCmd.OpenForm "TaskF", , , [TaskID] = Forms![TaskListF]![TaskID]

To fix it, I changed the code to:

DoCmd.OpenForm "TaskF", , , "[TaskID] =" & Forms![TaskListF]![TaskID]

If I use the above correction to the Macro, I continue to see the initial error.

---

Reply from Richard Rost:

If Access 2000 is writing the macro as you have shown above (the first one) then that is incorrect. The problem is that Access is creating bad code (go figure). This is one of the reasons I don't really like using macros ESPECIALLY in the older versions of Access (straight VBA coding is almost ALWAYS better). However, we don't start getting into VBA programming until Access 301.

Good catch, and good fix. That IS the correct solution, and that's what the macro should have written.