Run-Time Error 3061

[Perfac]

There may be many other errors on this fraction of my app. Please just look at the error I fail to solve so far.
1. If form f02PrchInvcs is opened, click on Close, the error should appear.
2. It is about Running Sum and the event under form current. Run-Time Error 3061. I "Googled" and read a bit but no solving yet.
3. The other form f02SlsInvcs is set up the same and does not return the same error.

[Micron]

Didn't download because basic trouble shooting of your code doesn't seem to have been employed. Always debug.print (don't forget to comment that out when done) your sql when you're testing or trouble shooting. If it looks right, proceed. If it looks right but fails, copy the printout, open a new query in sql view and paste it in. By printing out, your variables should have been replace with real values so pasting into a test query should not be a problem. Switch from sql view to datasheet view, and if it fails, the offending portion might even become highlighted in the sql view.

[Perfac]

I found software named "Stellar repair for Access". I ran this little test DB by that software. I normally do the basic trouble shooting (as much as what I learned about basic trouble shooting), but I know in this test there are a few errors, which I am busy with. I hoped it is an easy small fix. Some good man helped me say 5 years ago with the running sum and on my system being used this error does not come up. Thanks for your advice. I will try to comprehend and apply, and let you know.

[isladogs]

I've also not looked at your example app as I remember finding it difficult to follow on previous occasions.
Your update query syntax is wrong. It should be something like:

"UPDATE TableName SET FieldName = '" & NewValue & "' WHERE SomeCondition";

[Perfac]

I did note who helped me with running sum some years ago with a FiFo system and it is good, and I saved the exact sample what that person suggested. The code I posted above is exactly like he suggested, and it always worked, including the Update query syntax as you see it. But I am trying new changes to the way I want the Purchase Invoice, and I assume some changes caused this error. Thank you for the code you suggest, but because of my shortcoming's, I probably need spoon feeding or the exact way the code should look on the form.

[Gicu]

UPDATE (SELECT q02PrchsInvcsSub.Coment_IDq, q02PrchsInvcsSub.QuantityA, q02PrchsInvcsSub.PRunTotA FROM q02PrchsInvcsSub ORDER BY q02PrchsInvcsSub.Coment_IDq, q02PrchsInvcsSub.DocumentDateE, q02PrchsInvcsSub.PuinsuID) AS q02PrchsInvcsSubSorted SET q02PrchsInvcsSubSorted.PRunTotA = UpdateRunSum([Coment_IDq],[QuantityA])

The highlighted E needs to be an X, the name of the field in q02PrchsInvcsSub query is DocumentDateX:
DocumentDateX: DLookUp("DocumentDateE","q02PrchsInvcs","PurinvID =" & [Purinv_IDa])

Cheers,

[Perfac]

Thank you. There is another gremlin. I changed the names of fields like DocumentDateX which is now DocumentDateU. Sorry for that, but I guess all of the field names is in correct places now. It seems that you solved the issue of this thread, but I am working on the error below. When I am ready, I will post the small DB again. Earlier today I put in a few hours to transfer form f02PrchsInvcs from my old running system. It took some time because I made many changes over time, but it looks like it is working with the code as it was before your advice. But I am very happy with what you advised and will set it up that way.

It took me few hours to

[Perfac]

You helped me last week with the second Sub form on f02Journals. I first thought I want to add that to f02SlsInvcs and f02PrchsInvcs as well. My thoughts later were that it is best to have that set of sub account system on f02PrchInvcs only. But it is fine, I still have to finish that off.

[Perfac]

You could use this information as a test of capturing a purchase invoice. Select anything in the combo boxes, but his may help. Because of what we do about the subset of accounts there is a reason why calculations are now on the form and not in the query. There is a lengthy explanation for that. I am working at it now, we will see.

[Perfac]

It's likely that I miss something easy here again. For a moment I thought it was perfect, but my last effort resulted in error. Maybe just open f02PrchsInvcs on the newest post and try to capture the invoice. I don't know why yet, but it does not display the error capturing the first line on the sub form, but it does on the subsequent lines. Thanks.

[Gicu]

Sorry but I don't see\get errors, what I noticed is that the Sub Ledger Account Name gets reset and only displays for the current record because you are limiting the row source (cascading combo boxes). I have changed that to work OK by resetting the row source in the Enter and Exit events of the combo. For the duplicate error I would suggest you investigated the data in the tables that are part of the record source query as I believe the query (with the recordset set as dynaset inconsistent updates) is attempting the add a record that already exists.
Note: I had a look and I think the table in question is t09CombinedEntities; you already have a saved record COE0 that you use for the default value, so when the query for the subform adds the record in t02PrchsInvcsSub it will attempt to add a new record in t09CombinedEntities so you get the error. Try to remove this table from the recordsource (q02PrchsInvcsSub) as I don't think you use the fields in the subform, maybe just for some calculations but those could be replaced with dLokkups.

Cheers,

[Perfac]

Thank you. I was very ill today, slept 20 hours, wanted to call the undertaker, but now I am fine again. I see more errors now. In the test, in t09LedgerAccounts the record for Inventory seems to be deleted. I do not see a saved record COE0 and that it is the default value. I call these documents transaction files. They should not add records to t01CombinedEntities. I will test what you suggest about Dlookups.

[Perfac]

Sorry, I looked in t01CombinedEntities, not t09CombinedEntities in the test I posted to you. I see COE0 now and the default. In t09CombinedEntities where I work on that is different no record with COE0??? I don't know how it got there.

[Perfac]

It is fixed now. You are the best. Thank you.

[Perfac]

I am not sure what I did to cause this error. I added "Option Explicit" at the top of the code some time ago, but it always worked since then. Removing "Option explicit" seems to stop the message, but what should I do if it stays. Thank you.