Cannot add a row in access 2016 subform when I can in access 2007.

Question

First of all, I have checked the different properties allow entry and entry properties and the likes of the form and the sub form, everything is at yes.

Is there a new feature in access 2010 and up that can stop someone from adding a row in a subform?

Do I need to recreate such subform from the ground up to be able to use it since they may be too old.

The problem isn't the fact that I'm unable to add rows in all versions, only in a newer version of access.

---

My alert for registry key webbrowser

Answer 1

I'm only want some brainstorming for a start.

---

My alert for registry key webbrowser

Answer 2

Hi,

Are you opening the same physical file in both versions? Or, did you convert or upgraded the old file into a new version? If the latter, then maybe it's possible the design of the form has changed during the upgrade process. Are you able to compare the two?

Just a thought...

Answer 3

I actually opened the same file in both version, I even done a copy and tried to convert the copy, both of these failed.

Thanks, keep the ideas coming.

---

My alert for registry key webbrowser

Answer 4

Is this an original database and different Access versions or some other combination?

Are you working with an original form/subform or one that was copied and pasted/ imported?

Verify that the Master/Child links are correct.

---

Build a little, test a little

Answer 5

Hi ct2651,

you had asked,"Is there a new feature in access 2010 and up that can stop someone from adding a row in a subform?"

first shows us how you try to add the row in sub form?

by user interface or by code?

we will try to make a test and let you know about the result.

It is possible that something get changed between these two versions.

so if you provide the steps to reproduce the issue hen we can provide you the solution or a work around for that.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 6

The result that is valid in access 2007 is this one. (extension .accdb)

Like you see, we have a form that possess three sub form and in 2007, I can add rows to all of them.

In access 2016, the star icon meaning that I can add a row is not present.

How to reactivate this way of adding a row. It can't be by code since this is for a simple user.

Like I said, there must be something that changed how subform and form act between 2007 and 2016, but I don't find it.

---

My alert for registry key webbrowser

Answer 7

There seem to be two subform that are kind of put in union into the main form.

The two subforms don't appear with the same data in 2007 and 2016. One of the two subform is empty in 2007, that's the one that is used to add rows probably, and in 2016, the empty subform is full of the same data as the other one, the difference in name of the subform is only this:

Sous-Formulaire et Sous-Formulaire act

the act for active form is the one with the data, the one without the act is the empty ones that is not empty on 2016.

---

My alert for registry key webbrowser

Answer 8

The datasheet view of the subform are the ones that different between 2007 and 2016.

Like I said earlier the Sous-formulaire is the one that under datasheet view should be empty since it appear empty on 2007.

The Sous-formulaire act datasheet view have the data, and in 2016, both of these subform contain the same data instead of having one of them being empty.

---

My alert for registry key webbrowser

Answer 9

Hi ct2651,

from your description , I understand that one of the sub form in Access 2007 is empty.

when you try to open the same form in Access 2016 then the sub form contains the data and it is not empty as it was displayed in Access 2007.

did you try to check the source object of that sub form?

check that it is same as Access 2007.

are you able to insert the data in the sub form?

if yes then , we can say that it is just a difference between these two versions that displays the data differently.

if you are able to insert the data then it should have no problem.

but if you are not able to insert the data then let us know about that.

you can see in picture below is taken from Access 2016.

I can able to insert the data in sub form.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 10

Is your database split (ie: A front end for the user interface and a back end for the data)?

If split, is the Back-end Access, or something else such as SQL Server?

Have you verified that the folder containing the database on the Access 2016 machine has proper permissions?  Users need full permissions on that folder (you may see results as you are describing if the folder or file is read-only).

---

Miriam Bizup Access MVP

Answer 11

Ok, now this is even weirder...

The act sub form is linked to the request with the word act.

The non act sub form is linked to the request without the word act.

The act request only difference with the non act sql request is the number comp, that is not a unique number but does seem to be some kind of filter, and that filter works in 2007 and 2016 since I only saw the 0 number on the column of the datasheet view of this request.

The same data can be found in the non act request but without the column number comp since it was not called in the sql.

The non act sub form in access 2007 appear empty with the possibility to add an entry and in access 2016, the non act sub form appear with the same data has the act subform and I can't add data in it.

The two associated resquest have the same result in 2007 and 2016.

So the problem may come from the way a subform is taking the data contain into a request. (Maybe the rule for taking data from a request differ between 2007 and 2016, maybe the rule is lost from a version to another.) 

---

My alert for registry key webbrowser

Answer 12

Hi ct2651,

it is better if you post the sample database that can reproduce the issue on our side.

your description is not enough to get the idea what's the actual issue there.

we are just assuming the situation and not able to provide solid suggestion.

you can create a sample db with dummy data in it and upload it on any free file sharing website and share the link here.

we will try to access the file and try to check the issue.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 13

Yeah, I will try to do a dummy database file.

I will check if I can modify the tables, if yes, I will empty them all and modify only the one that we need to test.

I'm pretty sure at the moment that the problem lies with the SQLrequest that doesn't act the same in 2007 and 2016. (One of them is suppose to be empty with the possibility to add an entry, the other is full of data and can't add anything. In 2016, both of the request appear as full without the possibility to add anything.)

---

My alert for registry key webbrowser

Answer 14

Ok, here goes four image of what exactly is different between 2007 and 2016.

Next post will be the file.

If we solve the problem for Engagé sous formulaire, I can do the same correction for the other one too that is Dépensé.

---

My alert for registry key webbrowser

Answer 15

Heres the link to a dropbox folder with TestingDatabaseMSDN.accdb in it.

All the table possess only minimum dummy data and the VBA code is free of any sensitive data.

The goal here is making the form Engagé sous-formulaire acting the same way in 2007 and 2016.

The image just over this precise the difference between 2007 and 2016 even though it is the same file.

Of course, if you happen to have that star in 2016 (that show that you can add entry), my problem is probably from the group policies again.

TestingMSDN

---

My alert for registry key webbrowser

Answer 16

Engagé sous-formulaire without the mention act will be empty in 2007 but will appear with the same data as the Engagé sous-formulaire act in 2016.

that is the problem, the Engagé sous-formulaire need to appear empty with the possibility to add a row like in 2007.

---

My alert for registry key webbrowser

Answer 17

So, how is the testing?

---

My alert for registry key webbrowser

Answer 18

Hi ct2651,

I try to open your database with Office 2016.

it is displays the record as you mentioned above and we cant add new record in it.

I try to check the RecordSet type of the form. it is set as 'Dynaset'.

I try to change it and I find that when I set it as 'Dynaset (Inconsistent Updates)'.

it allows me to add new record.

so if you want to add new record to this form, you can try to change the Recordset type.

I have all latest version of Access from 2010 to 2016, but unfortunately I am not available with Access 2007.

so I am not able to make a test with it.

you can try to change the settings of the form let us know about the results.

when I open the form in design view then I find that drop down has assigned the data manually by typing in the Row Source.

do you just want to display nothing in the combobox when you load it? and then user can select one after that?

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 19

Ok, The record type that was there before you modify it doesn't act the same way in 2007 and in 2010 and others.

My software is in French, so I don't know the name in English, you should write it down in this thread so that others people are able to read it.

As for me, the rest of the document act the way it should in both 2016 and 2007 if I put the RecordSet French version from "Feuille de réponse dynamique" to "Feuille de réponse dynamique (MAJ globale)"

I don't know the difference, but that option is completely compatible.

---

My alert for registry key webbrowser

Answer 20

Oh, You already put the name in English,

Ok, I'll just repeat it here then.

RecordSet has to be set to Dynaset(inconsistent Update) to have the same behavior in 2007 and others.

---

My alert for registry key webbrowser