Home
Forums
New posts
Search forums
Articles
Latest reviews
Search resources
Members
Current visitors
Newsgroups
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Newsgroups
Microsoft Access
Microsoft Access VBA Modules
Interactivity between2 instances of Access
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Albert D.Kallal, post: 8227616"] Well, it seems to me that you should pre-link the new mde? The steps usually are re-link the mdb to the production back end create the mde. This mde is now pre-linked, and does not need to be linked at startup If you don't plan to have the mde pre-linked (or, cannot have the location pre-linked), then your startup code in the application needs to test/check for this situation anyway. I mean, your startup code has to test for this anyway, and you likely need some re-linking code in the application. So, I fail to see why you are trying to pre-link with your as it is now. Simply use the linked table manger, and then create the mde..and you are done (at least for the linking part). Well, if yoiu pre-link, then all you have to do is copy. Current project is now going to be you golive.mdb..not the actually mdb, so, this don't make sense.. Should not the above be passing the name of the mdb file you want to re-link? As I mentioned, this seems confusing anyway, and why not just pre-link BEFORE you make the mde? [/QUOTE]
Verification
Post reply
Home
Forums
Newsgroups
Microsoft Access
Microsoft Access VBA Modules
Interactivity between2 instances of Access
Top