Prevent users from adjusting subform label/field sizes (1 Viewer)

donkey9972

Registered User.
Local time
Today, 13:09
Joined
May 18, 2008
Messages
126
Hi, I have a form with a sub-form on it. I was wondering if there was a way to prevent users from constantly adjusting the sizes of the labels and fields within that sub-form?
 

Attachments

  • Screenshot 2024-12-21 224613.png
    Screenshot 2024-12-21 224613.png
    7.7 KB · Views: 9
Make it a Continuous form arranged to look like Datasheet.

But why is this an issue? Database should be split and each user have their own copy of frontend.
 
Due to security restrictions in place where I work, splitting is not an option.
 
If this db has multiple simultaneous users, you should plan on corruption of data and design. Or so I keep hearing that is expected. I have designed one multi-user db that wasn't split and in 4 years it never corrupted. But it was very small with no code, not even macros.
 
Last edited:
This db ionly used on one computer. There is multiple users, but only one can be logged in at a time. The current db we are using I made like 4 years ago. I have had no issues with it, it does have code.
 
Oh I like that idea. When I have a chance I will look over the link u provided. Ty for that idea.
 
Would security prohibit splitting db if both files are in same folder? You haven't had issues so far but it is still safer to split, even if only one user at a time.

Good luck with your project.
 
I have tried it. And what happens is the security warning pops up and says that type of file is not allowed. I work on a military base.
 
Last edited:
I have tiedit. And what happens is the security warning pops up and says that type of file is not allowed. I work on a military base.
download it from your home not on your workplace.
 
you can also use the Form's Timer event to re-instate each column in the datasheet.
open form Form1 on the demo db.
 

Attachments

I work on a military base.
First thing you should do then is write out exactly what you are trying to do, what issues it mitigates, and make sure you Email who ever is telling you this is prohibited your write up. Include 'And I am stopping by to get your signature that you have been advised'.

Most officers are smart enough to realize that you Emailing them "There is a problem" is enough to warrant looking at the problem. If you can show how to mitigate the problem and are asking to do so, most will either do so OR push it up to the person preventing it from happening.

I had fun watching an O3 end his career by not listening. Major Command didn't get the nice reports that had been coming in because this O3 decided they just were not that important.
 
Not clear whether you are happy for a user to resize/hide columns for their own purposes, just not save the changes. Or you Don’t want them to be able to resize at all.

If the latter use a continuous form as already suggested.

If the former note that changes to layouts are not saved unless the user saves the form (not talking about saving data). So perhaps some code to close the form without saving (not sure what that code would be, not at my computer right now, perhaps a button with code to close the form with save parameter set to no).

Easiest option is to use a .accde where forms cannot be saved. But that gives you a problem with an unsplit database as you would need to use a .accdb to make changes then import all the tables from the original .accde before creating a new .accde.

Curious to know the security reasons for not allowing the db to be split - an unsplit database is less secure than a split one and any app that utilises a database will be split as a matter of course, Access is pretty unique in allowing an unsplit app and you run the risk of losing everything if something does go wrong- so hopefully you have plenty of backups
 
See how to lock column sizes
 

Users who are viewing this thread

Back
Top Bottom