Navigation Form with subforms- Access asking me to save record

dferreira

Registered User.
Local time
Yesterday, 23:31
Joined
Sep 13, 2011
Messages
25
I have a navigation form with subforms within each tab. It works fine on my machine. But, my users on their machine, access asks them to save the record when going from one tab to another. Do you have any suggestions?
 
Do you have any code behind the forms? Are you dirtying the data? Is the question/warning about saving the form design changes or the data updates/changes?
 
no the user has not dirty the data. They are just navigating from one tab to another. It is happening during navigation. But it does not happened on my pc.
 
Thank you for replying. I would be willing to pay you to look at this issue.
 
What's the difference between your PC's configuration and theirs? Are they using Runtime? If you can't share a copy of your db here, we can hook using a screen sharing app. Shoot me an email, I might be able to assist you tonight.
 
Can we do it sometime tomorrow? I can show you what is going on. We can do Go To Meeting. let me know about what time you might be available tomorrow. I maid a slight change. The only difference of pcs is that they have Access 2016 and I have 2019. A lot of my customers are able to use my database that have 2010, 2013, etc. This is a new database, but works fine on my machine. I will give you some money via paypal for your time tomorrow.
 
no the user has not dirty the data. They are just navigating from one tab to another. It is happening during navigation. But it does not happened on my pc.
That doesn't really answer the question as to whether or not the prompt is to save changes to a record or changes to the form design.
Did you see the message yourself, or was it reported to you and is it certain the message is about a record? Nav forms are known to prompt to save design changes if the form contains a datasheet and the user alters things about the columns in that form.

Oh, and another thing that can cause a design change prompt is that the user applied a filter or sort on the datasheet.
However, if everyone is doing the same thing yet only some people are getting prompted, then I suspect there are different versions of Access involved. The ones experiencing the issue may be using older versions. This used to be a known issue years ago, but it doesn't happen in my version (2016).
 
Last edited by a moderator:
Can we do it sometime tomorrow? I can show you what is going on. We can do Go To Meeting. let me know about what time you might be available tomorrow. I maid a slight change. The only difference of pcs is that they have Access 2016 and I have 2019. A lot of my customers are able to use my database that have 2010, 2013, etc. This is a new database, but works fine on my machine. I will give you some money via paypal for your time tomorrow.
Okay, tomorrow sounds good. I'm on Pacific Time Zone. Shoot me an email for the invite. I am available at 9am PST.
PS. For some reason, this got stuck in my outbox and didn't get posted last night.
 
Micron, thanks for replying. In this case, the user is just navigating to the other tab. They have not made a change to the data in the sub-form that is a datasheet form. However when the form is opened I have code that sets the column sizes in the datasheet. Is that what is causing the problem? I have done this before. When I read your post, I wondered if that is causing the problem.
 
Likely. There is really no such thing as just "navigating to another form" with a nav form. This form can only hold one open subform at a time. You click another tab, you close the open subform and open the next one. Sounds to me like you are programmatically altering form design, then closing it when switching tabs, which provides the prompt. Some consider this a bug because it doesn't happen if the form is opened from the objects pane. I'd agree, especially since I tested a nav form with subform data sheet in my Access version and I don't get prompted. Then again, I was altering column width and sorting manually. Maybe it behaves differently if done by code.
 
Micron, thanks for replying. In this case, the user is just navigating to the other tab. They have not made a change to the data in the sub-form that is a datasheet form. However when the form is opened I have code that sets the column sizes in the datasheet. Is that what is causing the problem? I have done this before. When I read your post, I wondered if that is causing the problem.
Hi. What happens if you remove the code for resizing the column widths? If the problem goes away, then that's probably the cause of your issue. We just need to figure out why it's not causing a problem on your machine and see how we can do the same for your users.
 
If it turns out that your code is the problem but not on your machine, then I suspect there are different versions or builds of Access (or maybe of Office, but I don't know if that's relevant) between the machines. If that is the case and you need this column fixing code, I'm not sure there's any practical way around the issue but would be willing to try if you posted a db copy but I would test the code-altering effect on my db first. If it doesn't prompt me, there's probably no point. Opening in design/invisible, altering, saving then opening normally seems like a hack to me and might produce screen flicker, so I'd be looking for something else - or consider ditching the code.

There may be another approach, but since at this point I haven't experienced the issue, if you disable the code and they alter the columns, are they prompted to save design changes? If they say yes (or are not prompted) are those changes in effect when the form opens again? If not, set them in design and forget the code because the user is having no effect anyway. If they are being saved, then consider that sometimes as developers we try to impose too much control and need to ask, are the column properties on open all that important?
 
Man, I thought it was resolved. I took all of the code off that sets the column width and everything seemed fine! I read your post and then went to the database on their server and altered a column manually and it prompted me to save the changes. Yet, it does not ask me to save the changes on my machine with the code or without the code. Is it a property of some kind? This is so weird as it does not happen on my machine! Can you think of a property setting?
 
Man, I thought it was resolved. I took all of the code off that sets the column width and everything seemed fine! I read your post and then went to the database on their server and altered a column manually and it prompted me to save the changes. Yet, it does not ask me to save the changes on my machine with the code or without the code. Is it a property of some kind? This is so weird as it does not happen on my machine! Can you think of a property setting?
Hi. Based on this other discussion, could you please ask the user to reboot their computer and then try again? Just curious...
 
By any chance are you using a runtime version when you don't get prompted?
You didn't comment on the point of whether or not there are version differences between you and the others...
 
Hi. I found another thread discussing the same issue, and the concensus was it's a "bug" with using a Navigation Form. The accepted solution (from Albert Kallal) was to compile your app into a ACCDE (because design changes are not allowed there). Hope that helps...

PS. Of course, that still doesn't explain why it doesn't happen on your machine. If we could run your app on our machines, we can tell you if we get the same thing or not. Then, we could maybe figure out the difference between each machine's settings. Just a thought...
 
As I mentioned, this doesn't occur for me if I manually alter the column width so I just tested using code on open event. Datasheet column width alters but when I navigate off of the form, there's no prompt. There is an option "enable design changes to tables in datasheet view" which I thought might come in to play, but it didn't matter.
 
I have seen that before. You chose the rowsource option? It might be good to know that in case this comes up again.
Originally you stated that it happened on one pc and not another, so I alluded to Access versions but you didn't say if one was 2010 or not. Glad you got it solved though.

BTW, it's not an issue with navigation panes - it's navigation forms. They are 2 different things. Good luck with your project!
 
Actually, they had Access 2016 and I had 2019. So, it did not happen on my pc so it happens on previous versions. OMG, I did not realize that I said navigations pane, UGH, I mean Navigation forms. My bad. I know this difference, I just typed wrong. Thank you again both of you for responding. This was a weird problem.
 

Users who are viewing this thread

Back
Top Bottom