Problem display size boolean fields

%3CLINGO-SUB%20id%3D%22lingo-sub-2652141%22%20slang%3D%22en-US%22%3EProblem%20display%20size%20boolean%20fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2652141%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20started%20today%20to%20use%20Access%202016%20on%20a%20new%20computer%20(HP%2C%20windows%2010)%20and%20I%20am%20encoutering%20a%20problem%20which%20did%20not%20occure%20on%20my%20old%20computer%20(also%20HP%2C%20windows%2010).%20I%20use%20Office%20365.%3C%2FP%3E%3CP%3EThe%20size%20of%20the%20boxes%20of%20the%20boolean%20character%20fields%20are%20out%20of%20proportions%20and%20pixellised.%20They%20change%20size%20if%20I%20change%20the%20width%20of%20the%20fields%2C%20but%20I%20have%20to%20reduce%20at%20the%20max%20the%20width%20of%20the%20fields%20in%20order%20to%20get%20a%20normal%20box%20size%20and%20as%20a%20result%20I%20cannot%20read%20the%20title%20of%20the%20fields.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20checked%20my%20computer%20display%20setting%2C%20it's%20at%20125%25%20which%20is%20what%20is%20recommended%20by%20Windows%2010.%20I%20have%20contacted%20the%20online%20support%20of%20Microsoft%20and%20the%20agent%20took%20over%20my%26nbsp%3B%20computer%20to%20uninstall%20and%20install%20again%20Office%20365%2C%20it%20did%20not%20change%20anything.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20anyone%20ever%20encoutered%20this%20problem%20and%20found%20a%20solution%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2652141%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2657787%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20display%20size%20boolean%20fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2657787%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1129436%22%20target%3D%22_blank%22%3E%40Belisaire%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20that%20a%20form%20or%20a%20table%2Fquery%3F%3CBR%20%2F%3ECheck%20your%20error%20trapping%20settings%20in%20the%20Visual%20Basic%20Editor.%3CBR%20%2F%3EThe%20only%20time%20I've%20seen%20anything%20similar%20was%20when%20the%20setting%20was%20Break%20On%20All%20Errors.%3CBR%20%2F%3EIf%20that%20is%20the%20case%2C%20change%20to%20Break%20On%20Unhandled%20Errors%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Capture.PNG%22%20style%3D%22width%3A%20568px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F303876i8A187DDA943C7CB4%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Capture.PNG%22%20alt%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20its%20a%20form%20and%20that%20doesn't%20help%2C%20try%20decompiling%20your%20project%3A%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fwww.fmsinc.com%2Fmicrosoftaccess%2FPerformance%2FDecompile.asp%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EDecompile%20and%20Compact%20Your%20Microsoft%20Access%20Database%20to%20Improve%20Performance%20and%20Fix%20Corruption%20(fmsinc.com)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2659019%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20display%20size%20boolean%20fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2659019%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1007894%22%20target%3D%22_blank%22%3E%40isladogs%3C%2FA%3E%26nbsp%3Bthanks%20for%20your%20message.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20checked%20the%20Visual%20Basic%20Editor%20but%20the%20setting%20is%20already%20on%20%22%3CSPAN%3EBreak%20On%20Unhandled%20Errors%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20picture%20I%20am%20showing%20is%20from%20a%20table.%20However%2C%20I%20must%20precise%20%3A%20%3CSTRONG%3Ethis%20disturbing%20display%20of%20Boolean%20fields%20boxes%20occures%20anytime%20on%20Access%2C%20even%20on%20new%20database%3C%2FSTRONG%3E.%20It%20does%20not%20happen%20on%20my%20old%20computer...%20so%20could%20it%20be%20a%20problem%20of%20PC%20resolution%20%3F%20My%20new%20PC%20has%20a%20higher%20screen%20resolution%20than%20the%20former.%20But%20I'm%20sure%20plenty%20of%20Access%20users%20have%20even%20far%20better%20computer%20than%20mine%2C%20so%20I%20do%20not%20get%20why%20this%20problem%20is%20happening.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2659518%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20display%20size%20boolean%20fields%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2659518%22%20slang%3D%22en-US%22%3EDoes%20it%20still%20happen%20if%20you%20create%20a%20form%20or%20report%20based%20on%20the%20table%3F%3CBR%20%2F%3EIt%20mat%20be%20that%20there%20is%20an%20Access%20client%20setting%20on%20the%20new%20computer%20that%20is%20triggering%20this%20behaviour%20but%20I'm%20not%20sure%20what%20that%20would%20be.%20See%20if%20you%20can%20see%20any%20differences%20between%20the%20client%20settings%20on%20the%20two%20computers%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, I started today to use Access 2016 on a new computer (HP, windows 10) and I am encoutering a problem which did not occure on my old computer (also HP, windows 10). I use Office 365.

The size of the boxes of the boolean character fields are out of proportions and pixellised. They change size if I change the width of the fields, but I have to reduce at the max the width of the fields in order to get a normal box size and as a result I cannot read the title of the fields.

 

I have checked my computer display setting, it's at 125% which is what is recommended by Windows 10. I have contacted the online support of Microsoft and the agent took over my  computer to uninstall and install again Office 365, it did not change anything.

 

As anyone ever encoutered this problem and found a solution ?

12 Replies

@Belisaire 

Is that a form or a table/query?
Check your error trapping settings in the Visual Basic Editor.
The only time I've seen anything similar was when the setting was Break On All Errors.
If that is the case, change to Break On Unhandled Errors

 

Capture.PNG

 

If its a form and that doesn't help, try decompiling your project: Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption (fmsi...

@isladogs thanks for your message. 

 

I have checked the Visual Basic Editor but the setting is already on "Break On Unhandled Errors".

The picture I am showing is from a table. However, I must precise : this disturbing display of Boolean fields boxes occures anytime on Access, even on new database. It does not happen on my old computer... so could it be a problem of PC resolution ? My new PC has a higher screen resolution than the former. But I'm sure plenty of Access users have even far better computer than mine, so I do not get why this problem is happening.

Does it still happen if you create a form or report based on the table?
It mat be that there is an Access client setting on the new computer that is triggering this behaviour but I'm not sure what that would be. See if you can see any differences between the client settings on the two computers
If I create a form or a report based on the tables with Boolean fields, the boolean fields will have normal size boxes in the form or report...
I have made a comparison between the Access client setting on my new computer and the old one, but they are strictly the same since I use Microsoft 365 with both.
I should have asked you to check the appearance in a query and in a datasheet form as well.
The only other option settings I suggest you check are those for object designers and datasheets... but I'm not too optimistic that either will provide a solution.

Of course, I could say it doesn't matter as end users should never look at tables or queries directly. All interaction should be done using forms. Whilst that is true, I would also want to determine the cause. Have you tried compacting?

@isladogs 

Here is a picture of 1) a table (you can see that the "real size" box exist beneath the huge one) 2) a form (the boxes are smaller and do not change size if I change the size of the column) 3) a request (the size is almost correct and doesn't change if I change the size of the column).

Diplay_boolean_boxes_form.jpg

 

 

I have tried to "compact and repair" the database (several times) but nothing happens.

I now suspect the issue isn't within Access itself. You could check by putting checkboxes on an Excel user form and seeing whether the same result occurs. Or possibly by just exporting your table/query to Excel

Perhaps it is a glitch caused by an outdated driver for your graphics controller. Try updating the driver by looking at optional update in Windows update.
I have checked by putting checkboxes in Excel and they are displayed normally.
I have checked for an update but Windows does not find new ones, it seemes perfectly updated.
I would still suggest checking for an updated graphics driver. Other than that I'm out of ideas.
If you want to upload a cut down version of your database, I'm willing to look at it
Sorry. Did you mean you had already checked for an updated graphics driver?
I have a brand new PC, which is fully updated. I guess perhaps I don't know what you mean by "an updated graphics driver".

@Belisaire 

The graphics driver is software supplied with your computer which controls the display from your monitor. Periodically, updates may become available which you can download.

 

From the taskbar, go to All Settings ...Windows Update...then check for updates.
You may see a list of optional updates for various hardware drivers. For example, mine currently looks like this:

 

isladogs_0-1629546985721.png

As you have a new PC, there may not be any optional updates available for download.

Anyway investigate that and if you still have the issue, feel free to upload a cut down copy of your database showing the problem