LinkMasterFields Property issue: OLE server or ActiveX Control

[eranil84]

I get this "The LinkMasterFields Property setting has produced this error: 'A problem occurred while Microsoft Office Access was communicating with the OLE server or ActiveX Control' " error message when I try to add/edit line item to the subform and when I click OK, I am able to make changes, but the changes are not saved to the database.

This happens only when I try to use Access Database remotely. things work fine when I go to the server and add/edit line items in subform.

I have taken a copy of production database and pasted it in some other folder on production server itself. I added few fields to the table, modified Query and modified form containing subform. Then, I try to add line items. things work fine on server, but when I access the database from local machine, n try to add line items in subform, I get the above mentioned error. but the production database works fine remotely as well.

Please help!!!

[missinglinq]

Has this database been split into a front end/back end configuration, or are you trying to access a non-split database on a shared server?

Welcome to Bytes!

Linq ;0)>

[eranil84]

I am trying to access a non-split database on the server, the folder containing the database has been shared with few users who will make changes when required. I think issue occur when I make change to the form containing subform

[NeoPa]

You should never work on design changes of a database that's in use.

This is why splitting the FE & BE and releasing a new version of the (amended) FE is such a popular setup. I suggest you organise things the same way if you want to avoid such issues in future.

[eranil84]

what is FE & BE? can you suggest me some useful link to implement FE & BE?

Thanks a Ton!!!

[eranil84]

Sorry for not using the Common Sense... Front End & Back End you mean.. got it now.
I am working on it, hope it solves my problem.

[eranil84]

Hi Neopa,
I think this will solve my problem. However, I need a suggestion from you.

I have made changes in tables, forms and reports. How should I apply these changes to production databases.
Steps I have in mind for production implementation:
1) modify the production database tables in design mode
2) make a copy of the database (say db1.mdb) and modify forms, queries and report in that db. Doing so, because I have 12 databases to be modified.
3) create a front end database, link it to the production database tables. Then, import the forms, queries and reports from the db1.mdb database

Please suggest if it is OK or not. All the 12 databases are similar.

[NeoPa]

Sorry to use undeclared abbreviations. You got it though. That's exactly what I was talking about.

The usual method is to have a BE in place on the network. The FE is maintained on your development machine, and no-one else has access to it. Copies of the FE are on each user's machine. When a new release (tested on your machine) is ready the FE db that you've been working on is copied to each of the machines of the people who are to use it.

Does that sound like it makes sense?

[NeoPa]

I should add, when you have a situation that requires changes to the BE (Generally much rarer), then you simply do your testing work with a copy and release it to the network when ready. If, as is usually the case, the new BE only works with a new version of the FE, then you will need to release the FE to all the clients (as in previous post) at the same time as releasing the new BE.

[eranil84]

Yes. It does make sense. Unfortunately, This solution also didn't work for me.
I got the same error after deploying the FE to user's machine. No clue what's wrong... user can add line items to production db directly without FE, but after modifications, I get error message mentioned above.

[eranil84]

Please suggest something to fix this "The LinkMasterFields Property setting has produced this error" error message.

[NeoPa]

I'm afraid there is no information in your post that helps me think what your issue may be. I can't see what you've done, so if you want me to help you will need to be a little clearer in explaining what's changed and what you've done.

In case it helps, here's a link to some info on how to go about this splitting of the db into FE & BE databases (Front-End / Back-End (FE/BE)).

[eranil84]

I added 8 new fields to the database, and tested. Things working fine.
Then, I included those fields in the query. Then, also, things were fine.
Then, I opened the form containing sub form in design view and added new labels and text boxes for new fields.

When I opened the form and trying edit or add line items in sub form. it gives error. No changes made to sub form. However, when I try the same by logging onto server using remote desktop, it works well. How can I send you screenshot, data, etc.

Thanks a lot.

[NeoPa]

@eranil84
You seem to be referring to a form (which seems to have a subform associated) without any previous introduction to it. I imagine it must be some table maintenance form. I have no information as to table layout. I have very little information as to what types of changes were attempted, and how.

I feel very much in the dark, so entirely unable to help.

To attach items to a post, scroll down when in the reply page (not quick reply) and click on the Manage Attachments button.

Remember, as I have no access to your database, and no way of looking over your shoulder, I'm entirely dependent on the quality, accuracy and clarity of your explanations (/questions).

[eranil84]

Hi Neopa,

Note: My machine (developer) has an English version of office 2003. The server and the User has a Chinese version of office 2003 installed. So, in order to avoid version issue, I am doing the changes on server itself using remote desktop connection.

Please find attached the ePRScreen.zip file containing a word doc. This document might help you understand my problem better.

Thanks a ton for all the help.

[NeoPa]

Sorry I haven't replied sooner. I've looked a couple of times but when I haven't had much time available. I will see what I can do to have a proper look at this sometime soon, but my gut feeling from what I have seen, is that I'm unlikely to be able to help.

I will post again when I've had a better look, one way or the other.

[eranil84]

Hi Neopa, Thanks a lot for your help and support. It was first time I was using MS-Access and I learned a lot (BE/FE) from you. I got a solution to my problem. Instead of editing the existing forms, I created new forms from scratch and it worked for me.

Regards,
Anil Kumar

[NeoPa]

That's good to hear Anil. I admit I was a little confused by this one.

If you've sorted it out yourself I can relax :)

PS. I'm very pleased to hear you've been helped by using this site. I must admit that I have been too.