Solved Prevent users from adjusting subform label/field sizes

[donkey9972]

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?

 

[June7]

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.

 

[donkey9972]

Due to security restrictions in place where I work, splitting is not an option.

 

[June7]

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.

 

[donkey9972]

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.

 

[June7]

Alternative is to keep Datasheet, let users adjust as they wish then when form closes (or maybe when opening), use code to set column widths and maybe order because changing order is also a feature of Datasheet. https://www.access-programmers.co.u...to-set-column-width-in-datasheet-view.137689/

 

[donkey9972]

Oh I like that idea. When I have a chance I will look over the link u provided. Ty for that idea.

 

[June7]

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.

 

[donkey9972]

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.

 

[arnelgp]

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.

 

[arnelgp]

you can also use the Form's Timer event to re-instate each column in the datasheet.
open form Form1 on the demo db.

 

[Mark_]

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.

 

[CJ_London]

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

 

[MajP]

See how to lock column sizes

You Can Do That with Datasheets? - vb123.com

Everyone who uses datasheets knows they’re powerful, but very few people know all of the things you can do with them. Michael Kaplan pulls out a handful of tricks from the unlocked Access 97 wizards that can help you really … Continue reading →

vb123.com

 

[June7]

CJ, good catch. I tested this with a subform in Datasheet.
Code behind main form: Docmd.Close , , acSaveNo
Datasheet changes are not saved.
Nice.
Disable the X close: CloseButton set to No
Don't even show: ControlBox set to No

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.

You tried what? Just copying a file into folder?

 

[The_Doc_Man]

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.

I worked for 28 1/2 years with the U.S. Navy, different department names, but always associated with the Navy Reserves, and split databases were NEVER an issue. We had an Access front-end with an SQL Server back-end (therefore certainly split) that ran a BUMED (medical) personnel management program for Navy officer medical school scholarships. I had a pure Access application with a simple two-way split that helped track and manage computer system compliance with mandated and optional security hardening activities. It only took me a couple of sessions with the IT head to calm him down and leave us alone.

1. Note the exact message that you get. If it is a "security center" message we can advise you how to shut that up. If the security warning pops up that says the file type or action is not allowed, note the reason it gives, by site policy or by a specific department, you may still have a way out.
2. Tell your supervisor or whoever wants that DB that in order to stabilize the database, you need to split it in a certain way that is standardized and performed by the Access database splitter built-in tool. (I.e. no special processing by a third-party product and no manual processing.)
3. Tell your supervisor that if you split it, you will be able to allow multiple simultaneous users fairly cleanly (with our help.)
4. Tell any of your IT people who object to this idea to make a list of questions and come back here with that list so that we can answer their objections. We will be able to describe how to manage permissions very precisely regarding who can and who can't use the DB, using methods that ARE approved by DOD rules.
5. IF the problem is that you are running on a machine with SECRET or higher clearance, you are going to be in a world of hurt anyway, as Access is not usually considered compliant with that level of security.
6. The REAL trick here is that you think (and probably are correct) that you don't have enough clout to make something good happen. But if the persons who want this can be enticed with potential improvements, THEY might have enough clout to help you politically while you continue with the technical and implementation issues. Don't go banging your head against a brick wall. Let someone else have that fun.

 

[Pat Hartman]

Due to security restrictions in place where I work, splitting is not an option.

Talk about penny wise and pound foolish. That is an idiotic position for the PTB to take. Doc has offered excellent advice to get past the red tape.