Errors after importing Form

[Middlemarch]

Two of us use the same DB and I've made some changes and sent the other party a Form via Access External Data-New Data Source.



Now instances of "." need to be changed to "!" and references to controls need "Me!" added. Only his his DB, mine is still okay.

Perhaps someone knows why this is, and if there's any way to fix it so each one doesn't need changing ?

[orange]

Please tell us more about "Two of us use the same DB"...details please.
Common Backend? Same/different Frontend? Why separate databases specifically-if that is your situation?

You can SaveAsText the form(s) involved. You can use a text editor to change Me. to Me! etc (or whatever...) as required. Once finished with the editing, you can use LoadFromText to load the revised form. Google for examples.

[Micron]

The bang operator provides late bound access to the default member of the object that precedes it. The dot is used to early bind the reference(s).
Put another way, if your form control name is "txtName" and you code "Me!txtNaem" and compile the code, the mistake will not be caught; not until a line containing that mistake is executed. That's why I would never use Me! over Me. If however you use Me.txtNaem and compile, the mistake will be caught.

If that code won't work on one pc without using ! then it suggests to me there is some sort of library reference problem. Another possibility would be that the code reference and control name are out of sync on the copied form, but I don't see how using ! should resolve that. IMO if the other party needs a form you have created or modified, they should be the one pulling it in to their db, not you sending it.

This also makes me wonder how the distribution of front end objects is being handled. If the other party is using the same front end (the db is split, yes??) then that is what should be distributed.

[Middlemarch]

Thanks for replies. Looks like there's no magic fix. I take from the above I'm using "early biding" and "late binding" is what's required. And changes must be made, possibly in a text editor.
It happens as something is "out of sync" or a reference problem. They're separate databases as we're in two different countries.
There is no backend, it's one same db, but with one Form changed. And that won't work, we can conclude? So I think rather than sending just the Form I'll send the whole db.

[Micron]

Your db's should be split; no question. Corrupt that db and you may lose everything, including your data.

If you need to send a db, send the front end (fe) with the forms/reports/queries and vb project. VB editor has a Find/Replace feature so I don't think you need a text editor. You could change one using F&R and send that. It's still a mystery to me why one db needs ! vs . unless maybe the ! db is missing a reference for the vb project.