Access Split form sub datasheet transaction issue when deleting, copying records

Hi

I have a database which is used to keep track of industrial objects for a project. For each record (object) there are a connecting revision table (one to many) which is utilized to keep track of data changes for the object (revision handeling).

Data structure:
-Main Table
*Revision Table

The interface is a split form with a subdatasheet form for the revision handeling. I want the user to have the possibility to work in both views (form view and datasheet view).

Now to the issue, when deleting or copying records in the subdatasheet form I get the notification "This Operation is not supported within transactions" and the operation is not carried out (even if it looks like the records are deleted).
When directly in datasheet view for the main form this problem does not occur.

I have made a video of the issue
Johan LüningAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PatHartmanCommented:
A split form is a specialized Access form that shows one record on the main form and multiple records on the datasheet subform, one of which is the main form record.  Is this actually what you have or are you just calling this form a  "split" form because it resembles one?   What you should have is a main form bound to the parent table (or query) with a subform in ds view bound to the child table (or query).
0
Johan LüningAuthor Commented:
Thanks for your answer.
It is an actual splitform, I want the user to be able to edit data in both views. The main form have a subform for revision handeling (user manually log data changes of value). So its is built as you describe.

Design viewForm view
0
PatHartmanCommented:
I'm pretty sure that you are not going to be able to resolve this if you stick with the Access split form.  It works the way it wants to work and I think it is having trouble with the subsubform.  

You will probably need to build your own split form manually.  Create an unbound main form.  Add a ds view subform and a single view subform with the dsview subsubform.  You can then make it work like a split form - except you won't get the splitter feature with just a couple of lines of code.  Add a hidden field to the unbound form.  In the current event of the ds view form, copy the record ID to the hidden field and then requery the single view subform.  The RecordSource query of the single view subform should use the hidden textbox as criteria.

Select ...
From ...
Where MyID = Forms!mainform!txthiddenID;
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.