Search results

Yeah but my buttons look better with ThemeBlue. Themes do some funky stuff with buttons that I've never quite been able to reproduce with fixed formatting and I've found that they don't always translate well to another theme.

OK now I know how I got Aptos. The db I inherited was very slow compacting and opening the VBE so I created a new db and imported all the objects. This is something I often need to do on large applications. In future I'll create the new db with ThemeBlue.

@Colin Thanks for taking the time to post all the great info. Peter Doering's registry script saves the day. Brilliant. My previous attempt managed to take regress me from 2508 to 2507. Current channel now takes me up to 2509. Yeh! Installed Beta 2510 on me secondary dev machine. Ready to test...

I've now added the Text Fomatting group to the Datashseet tab on the ribbon. This would seen the logical place for users to find it. I'm still a little intrigued as to how Aptos inflicted itself into these forms. Calibri was the default font for Access/Office/365, that changed to Aptos at some...

Thanks Colin, changing the font/fontsize using the ribbon resolves the issue.

The main issue for me, is that the cursor appears one character to the right of where it actually is. This affects Aptos <=11 but as you say, >11 works OK. I can fix this in controls but for datasheet view, there is no option for fontname and I can't even get ds forms to respect my setting for...

there is plenty of info on Outlook, Word and PDFs but nothing on Access. It is the rendering in Access controls and datasheets that's causing me grief.

Does anyone know if MS have, or are about to, release a fix for the Aptos font rendering issue? Or does anyone know a trick to setting it back to Calibri for Access. If not then I'll write some code to change every control's fontname. sigh!

Greg Regan has done some excellent presentations for the Access User Group on modern form design, just search on YT for "access user groups greg regan". He preseneted yesterday on using SyncFusion's (free) Metro 5 to create icon images for this purpose. I hope to have that edited and posted in...

Thanks Minty, OK, so the View's "Primary Key" is just an index not a constraint. Or is it? Why do they call it a PK? Why don't they just call it a unique index? Why is the index name prefixed with double underscores (another question entirely). We know that when you create a PK constraint in...

I'm about to do a thorough testing on Server Views, They've been a bit flaky ever since the RefreshLink issue. I worked my way around all that at the time and everything works... mostly. This week I imported all my objects including tdf links into a fresh container. After that I had one message...

You can do this using GDI. see Access Gantt Chart for a demo. This demo is a Gantt chart but pivot and the same principles apply to a Kanban board

Wow, I just had a flashback to when I first learned about concatenation with + and &. I recall when and where I was. I was on a beach. It was 1994. Same time I learned about 'Or Is Null'. I just can't remember the name of the book. More of a booklet as I recall. I keep thinking Speed Ferret but...

good point although I'm so far not having an issue with Chr(!0), Chr(30) being embedded. With two fields I used to concatenate them with a vbNewLine anyway and use the control's Can Grow on reports to handle layout. Do you have a better method to handle printing when you have two fields but...

I'm rather inclined to use one address field which is a free for all that may include Street Name, Street Number, Building Name, PO Box or whatever. This field allows multiple lines. Then separate fields for City, Post/Zip Code, State and Country which are validated from lists.

If you can't modify them using VBA then I can't use them. In my applications, schema modifications are all done by code. No-one manually hacks into a BE to modify objects. That would be contrary to the principles of SDLC. Access forms do some pretty amazing but unintuitive things. LIke allow...

so when he said "Relationship" he really meant "Join". a relationship is a database constraint while a join is just SQL and can be adhoc much easier to follow if we, as professional developers, used the correct nomenclature.

I don't get what you mean, can you give an example?

I was just thinking about all the things to consider when migrating. For example, An Access index has a boolean option for Ignore Null while in SS you need to apply a filter to the index (I think SSMA now does that) but you should only do that if the column allows nulls. FKs in SS have...

and by "connections" you mean relationships? I really only work with SQL Server dbs so I haven't used Lookups since Access Web Apps. I'd kinda forgotten about them. Do they create some kind of relationship in the background? (For Access tables. Obviously not applicable to SS) or are they visible...