Solved Interface seems dumbed down (1 Viewer)

dibblermail

New member
Local time
Today, 20:33
Joined
Jan 10, 2025
Messages
27
Hi, this seems like a stupid question, but...

I'm building my first attempts at a database and when watching videos I've noticed an obvious difference. Where's the rest of the icons on my version?

As you can see below, I don't have anywhere near the same number of icons to choose from & we both appear to be on the same version (2007)

Also, when selecting sub form, the version he's using doesn't behave how mine does. It's like I'm in a light version.


1741767733432.png
 
As you can see below, I don't have anywhere near the same number of icons to choose from & we both appear to be on the same version (2007)

1.) The two windows are not of the same version. The blueish window in the front is Access 2007, the white/grey window in the background is at least Access 2019 and might be even the most recent version of Access 365 as of today.

2.) You do have nearly the same number of icons. Actually, I see just three icons which are in the background Access window but not in the front. - These three, Themes, Modern Charts and Insert Image, are both for functionality, which wasn't available in Access 2007 yet.

As for the different sub form behavior, you should elaborate on these differences. Maybe there is a logical explanation for these.
 
1.) The two windows are not of the same version. The blueish window in the front is Access 2007, the white/grey window in the background is at least Access 2019 and might be even the most recent version of Access 365 as of today.

2.) You do have nearly the same number of icons. Actually, I see just three icons which are in the background Access window but not in the front. - These three, Themes, Modern Charts and Insert Image, are both for functionality, which wasn't available in Access 2007 yet.

As for the different sub form behavior, you should elaborate on these differences. Maybe there is a logical explanation for these.
so the "2007" showing on mine at the top of the window is the file format?
 
I agree with sonic8. Your screens show two different versions of MS Office and Access.

What are you looking to do?
 
It's all right, I was thrown sideways by it saying 2007 at the top.

Now that I've watched a 2017 video it makes much more sense.

Thanks to everyone that took the time to reply, much appreciated.
 
Last edited:
It's all right, I was thrown sideways by it saying 2007 at the top.

Now that I've watched a 2017 video it makes much more sense.

Thanks to everyone that took the time to reply, much appreciated.
2007 was the version in which the accdb format replaced the mdb format for Access files. The name "2007-2016 file format" reflects that.

Since 2016, the way Microsoft refers to the Access file format reflects a different approach to naming its versions. The name "2007-2016 file format" reflects that.

It's somewhat interesting, if a bit complicated, so if you want to learn more about it, an internet search can turn up a number of resources that will help shed light on it.
 
The children who run MS believe that change for the sake of change spurs sales so sorry but you'll have to learn to live with it. EVERY new version of Access (and Office in general) has productive changes and improvements but also nuisance, stupid, meaningless changes that will drive you nuts. Once you get better acquainted with Access, you may still be frustrated as you look for where a certain command got moved to but it does become easier with time.
 
Really Access has been very good since A97. A2003 changed the horizontal and vertical structure of the database window (infuriating at first)and added some useful functionality.

Further versions have added some further features none of which are absolutely essential. The tweak that lets you add formatting flags to turn text boxes into rich text boxes is user friendly. The inclusion of anchors to fix control positions relative to edges of a form is also worth knowing about, as it adds polish to an app.

I tend to develop in A2003 so I don't actually use much new stuff. I still use a modified version of the A2003 switchboard for example, which I find far more intuitive than later versions. It would be interesting to know what real changes power users and developers find indispensable. :D
 
I tend to develop in A2003 so I don't actually use much new stuff. I still use a modified version of the A2003 switchboard for example, which I find far more intuitive than later versions. It would be interesting to know what real changes power users and developers find indispensable. :D
Take a look at some of the samples I built based on the A97 (fixed at 8) and A2003 (continuous) versions as well as a completely custom one I created that supports user defined Icons as buttons. I even made a fixed version that was big buttons rather than a list with button and text.


 
@Pat Hartman

Yes, my switchboard does similar things to yours. My standard is 25 items - 3 columns of 8, plus a "return" option. I do have big commercial apps and do need that many options.

I meant more what new functions are included in A365 that developers find indispensable, but which weren't present in A2003.

For instance, I have taken an A2003 database and developed it further in A365 to be able to add rich text formatting to include within emails. I do find the rtf text useful. It would be useful to incorporate some control anchoring within my apps, but that would be a lot of work. I just don't know exactly what else might be worth having.
 
Last edited:
The children who run MS believe that change for the sake of change spurs sales

Just an observation, Pat, that either there is a quirk of human nature that does this, or a lot of MS children were once U.S. military children. I saw from first-hand observation that the military mind can't handle the status quo very well either, and makes change just in the hopes of shaking things up to spur performance. I don't want this to devolve into a political slug-fest, but what Donald Trump is doing in Washington is perfectly aligned with this concept. Perhaps it is in line with the "percussive engineering" method of fixing things: If it ain't broke, don't fix it. If it IS broke, first give it a good whack to see what falls out.
 

Users who are viewing this thread

Back
Top Bottom