Recordset is locked for editing (DAO)

[Denburt]

Something like Dsum(Cost; qryCostPerEachI ngredient; IDArticle = varIDArticle) ?

Well, that works, but it gives me multiple records. Then again, I could just use the "Select Distinct in the SQL string....?

I am sorry you have me completely lost now. I read post #12 and you were referring to query A and query B and mentioning items not even in the database that you posted or in the code you have previously posted. The database you posted has one query that sums your figures up but it isn't used in the code either so excuse me if I am a little confused as to where we or you are currently and what your goal is at this point. Maybe you can rephrase your question and I will see if I can help.

[NeoPa]

Martin,

I plan to look at this again this evening. Could you do me a favour and explain your current situation and question as clearly as you can and how it relates to the database attached. I will be able to look at that when I get home, but I haven't had a chance to yet as I'm at work.

[Martin Lang]

Sorry that I haven't expressed this clearly enough :) I really appreciate your help and kind offers :) No reason to excuse yourself as it is me who complicates things with my badly defined problems :)

I used the terms query A and query B to simplify my Norwegian structure in English :) And your advice has really helped me to understand why the original error message appeared in the code I posted in #4.

If you have a look in post #4, on row 10, I have a Select string. The select string consist of several tables/queries. "Query B" was making the error. The reason why was that I had ticked "totals" in design view(if you understand what I mean, not sure if it is the correct translation to the English version of Access), but a new row pops up in design view) . "Totals" locks all posts for editing. That was why I couldn't run my original code (post #4), where I wanted to edit the DAO recordsource which query B locked.

I think I will be able to solve it by myself now. I will come back to you if not. Anyway I will let you know how it goes.

Thanks to both of you :) I really appreciate it!

Martin

[Denburt]

If you have a look in post #4, on row 10, I have a Select string. The select string consist of several tables/queries. "Query B" was making the error. The reason why was that I had ticked "totals" in design view(if you understand what I mean, not sure if it is the correct translation to the English version of Access), but a new row pops up in design view) . "Totals" locks all posts for editing. That was why I couldn't run my original code (post #4), where I wanted to edit the DAO recordsource which query B locked.

Ah I see it, you just need to open a recordset for "Select IDRåvare from Halvfabrikat where IDHalvfabrikat = " & rsI!IDArtikkel & "" then you can update IDRåvare instead of trying to update the RSI recordset since you can't update RSI for reasons specified earlier.

Good luck hope all goes well let us know if there is anything else we can do.

[Martin Lang]

Ah I see it, you just need to open a recordset for "Select IDRåvare from Halvfabrikat where IDHalvfabrikat = " & rsI!IDArtikkel & "" then you can update IDRåvare instead of trying to update the RSI recordset since you can't update RSI for reasons specified earlier.

Good luck hope all goes well let us know if there is anything else we can do.

Thank you Denburt,

This is my first "real" database. A lot of lessons learned. My plan is to rebuild it at a later point when I am sufficiently motivated. Now, it is more about solutions that works and less the most optimal solutions.

So I went for a dummytablesolut ion where data is temporary stored. Will look deeper into this issue at a later point. Till then, hopefully these things have matured for me :)

Thank you for your friendly offer. I am so glad that people like you, Nico and NeoPa exists!

Have a nice evening, or maybe it is day where you are :)

Martin

[Denburt]

Thank you Denburt,

This is my first "real" database. A lot of lessons learned. My plan is to rebuild it at a later point when I am sufficiently motivated. Now, it is more about solutions that works and less the most optimal solutions.

So I went for a dummytablesolut ion where data is temporary stored. Will look deeper into this issue at a later point. Till then, hopefully these things have matured for me :)

Thank you for your friendly offer. I am so glad that people like you, Nico and NeoPa exists!

Have a nice evening, or maybe it is day where you are :)

Martin

I am just glad I could help.

Everyone has to start somewhere, and I know I have had to stop and say wait I have an issue.... That's one reason I decided to help on this board the members were all so willing to help me whenever I have had or have an issue or two come up.

You have a good evening as well and again I am glad you have a working solution.

[NeoPa]

Martin Lang: Sorry that I haven't expressed this clearly enough :) I really appreciate your help and kind offers :) No reason to excuse yourself as it is me who complicates things with my badly defined problems :)

That's probably a little harsh on yourself Martin. Defining problems clearly is a struggle for most people who speak English natively. Yours are always well explained and it's clear you have gone to some trouble to do that as well as you can. I was simply alluding to the fact that the later situation wasn't so clear related to the attached database. Easily done, and no longer a problem anyway.

Martin Lang: If you have a look in post #4, on row 10, I have a Select string. The select string consist of several tables/queries. "Query B" was making the error. The reason why was that I had ticked "totals" in design view(if you understand what I mean, not sure if it is the correct translation to the English version of Access), but a new row pops up in design view) . "Totals" locks all posts for editing. That was why I couldn't run my original code (post #4), where I wanted to edit the DAO recordsource which query B locked.

That makes perfect sense Martin. In SQL that translates to a GROUP BY clause (which is quite common). Now, when you see that phrase mentioned you'll know it's about using Totals in a query :)

By the way, I'm very pleased you have managed to get a solution, and please post more questions if you have them.

[Denburt]

That's probably a little harsh on yourself Martin. Defining problems clearly is a struggle for most people who speak English natively. Yours are always well explained and it's clear you have gone to some trouble to do that as well as you can. I was simply alluding to the fact that the later situation wasn't so clear related to the attached database. Easily done, and no longer a problem anyway.

That makes perfect sense Martin. In SQL that translates to a GROUP BY clause (which is quite common). Now, when you see that phrase mentionned you'll know it's about using Totals in a query :)

By the way, I'm very pleased you have managed to get a solution, and please post more questions if you have them.

Very well put NeoPa! If only I could put things so eloquently. :)

Oh and Martin I wanted you to know I thought you explained things quite well by the way. Sometimes it can be difficult to get a point across no matter who we are or who we are talking to.

[Martin Lang]

Well, that is good to hear. Thank you. I will definitely come back whenever I am struggling with a new problem. Take care both of you :)