I'm going to try writing the code in VBA instead and see if that works.
You can also try the convert macro to vba tool
(ACC2010)
Open the form in design mode.
Select the control with the embedded macro
In the standard ribbon>Form Design Tools>Tools>Convert Form's Macros to Visual Basic.
Should convert all of the Macros associated with the from into the VBA equivalent. Not pretty coding by any means and often not the most effecient conversions; hoewever, it can save you alot of time.
Btw I'm using Access 2010, not 2007.
Sorry, don't know where I got that 2007 from. I'm blaming the grimlins (^_^)
As far as a linking issue, why would I be able to get the form open from design view if there was a linking error?
Just a guess based upon an old issue I encounted in my ACC2003 days. The forms worked just fine on my pc; hoewever, not on my bosse's. Turns out that I had some macros behind the buttons (used the wizard back then and didn't realize the limits of Macros). Seems that the forms would error when opened via code or directly but not indirectly via the design. Re-linked the tables and the issue went away... go figure... when you've been at this for 20+years you get to see some unique stuff.
I've had things that work on my PC at home and not at Work - other than a network connection, same setup.
I should also add that many of the forms that are giving me an issue are unbound forms that I use to create filter strings to open a report with.
So the macros pull information from the form and then attempt to open other forms?
As jimatqsi mentions; Do you have any on-open/load events? Do your other users have the security pop-up?