What are the top things you would like to see in a future version of Access?

I have actually been pasting all of the suggestions back into the first post so it is easier to read through everything. As far as the ribbon goes, I haven't really worked with it at all so I don't actually have an opinion, but do you think it might be better to just scrap the whole thing? I know one thing George suggested about 2007 was just going back to the way 2003 looks and feels . . .

hi,

I like the ribbon. Definately not to be removed. The ribbon does give a dynamic approach to an interface as you do get more useable screen area without and buttons on the form. Moreso when it all changes to suit to current form and without extra tabs. It needs more attention though and most gripes are mainly because it's not easy to manipulate. I had to crash course myself on xml and callbacks over a weekend to get results but think it's great. Sure the 2003 version is ok but things move on. If there was an easier way builtbin, I'm sure everyone would love it. Vs handles it buts quite hard to manage your callbacks to your access db from a built vs ribbon.

Nigel
 
I can't believe I didn't think of this before.

Completely eliminate macros as they currently exist. Adopt the Excel/Word macro paradigm (using VBA) and institute a macro recorder. Integrate Application level commands into the "macro" recorder (i.e. split a database, etc.).

If I may expand just a bit:

Do provide a list of common functionality to select from and automagically write the VBA code for it. (e.g. select "Move to a record" from one list of different actions, then type in criteria, press OK and pesto! VBA code for what you need to do!) This way, people still have the GUI functionality of macros as exists in Access but is still VBA coding, full stop.


Also, I originally didn't mention it earlier because it was already implied in my another suggestion about "Make it an add-on to VS", but just in case it doesn't go that route, scrap the VBA and replace it with VB.NET or whatever it is they're using in VSTO....
 
Last edited:
hi,

I like the ribbon. Definately not to be removed. The ribbon does give a dynamic approach to an interface as you do get more useable screen area without and buttons on the form. Moreso when it all changes to suit to current form and without extra tabs. It needs more attention though and most gripes are mainly because it's not easy to manipulate. I had to crash course myself on xml and callbacks over a weekend to get results but think it's great. Sure the 2003 version is ok but things move on. If there was an easier way builtbin, I'm sure everyone would love it. Vs handles it buts quite hard to manage your callbacks to your access db from a built vs ribbon.

Nigel

Well like I said, I haven't made the leap yet, so it is good to hear that there are some nice things about the ribbon. Hopefully it will be easier to use in the next version . . .
 
If I may expand just a bit:

Do provide a list of common functionality to select from and automagically write the VBA code for it. (e.g. select "Move to a record" from one list of different actions, then type in criteria, press OK and pesto! VBA code for what you need to do!) This way, people still have the GUI functionality of macros as exists in Access but is still VBA coding, full stop.


Also, I originally didn't mention it earlier because it was already implied in my another suggestion about "Make it an add-on to VS", but just in case it doesn't go that route, scrap the VBA and replace it with VB.NET or whatever it is they're using in VSTO....

What's wrong with VBA?
 
Not a suggestion pertaining to the thread, but I think it may also be very helpful to have some kind of poll to help us know which suggestions given so far are more popular and thus pritorize the list and provide some ground for MS to stand on when they try to figure out what they want to do with the next version. (Especially that I have this feeling they totally missed the mark with 2007.)
 
Not a suggestion pertaining to the thread, but I think it may also be very helpful to have some kind of poll to help us know which suggestions given so far are more popular and thus pritorize the list and provide some ground for MS to stand on when they try to figure out what they want to do with the next version. (Especially that I have this feeling they totally missed the mark with 2007.)


Hmmm. I could start another thread that is a poll, but I have a feeling there won't be enough options to cover everything . . . Or everyone could just post with their vote, and I could summarize it all at the top . . .
 
What's wrong with VBA?

Now I realize I did already say that: "Make it fully object-oriented", which is the main point of my discontent with VBA. There's no polymorphism, inheritance, and you can't instance a form as a class (at least not as straightforward), and forget about doing the same with controls. Data type is also another thing that can be improved on, especially with UDT. Oh, yeah and definitely do away with that archaic "On Error GoTo..." and use Try/Catch block.
 
Now I realize I did already say that: "Make it fully object-oriented", which is the main point of my discontent with VBA. There's no polymorphism, inheritance, and you can't instance a form as a class (at least not as straightforward), and forget about doing the same with controls. Data type is also another thing that can be improved on, especially with UDT.


Is it really necessary to throw VBA out entirely though? Can't it be improved upon?
 
Hmmm. I could start another thread that is a poll, but I have a feeling there won't be enough options to cover everything . . . Or everyone could just post with their vote, and I could summarize it all at the top . . .

I think so, too. Two ideas: Use a free online quiz service (e.g. surverymonkey.com), so it does the summary for you (some may cap number of responses for free) or use a Google spreadsheet which everyone can fill in their votes...
 
Hmmm. I could start another thread that is a poll, but I have a feeling there won't be enough options to cover everything . . . Or everyone could just post with their vote, and I could summarize it all at the top . . .

maybe access could have an auto polling feature to handle polling about access:eek:

Ns
 
maybe access could have an auto polling feature to handle polling about access:eek:

Ns
Now you're just having fun at my expense :D
It's ok, I don't mind.

I marked my top 5 most-wanted on the spreadsheet. I will wait until tomorrow and then post back with whatever results I have gathered by then.
 
I didn't see the 5 votes when I voted, so I removed the excess numbers of my votes and placed a note.. :)
 
I didn't see the 5 votes when I voted, so I removed the excess numbers of my votes and placed a note.. :)

I was just putting a "1" for "1 person voted for this" next to the ones I think are the most important. I figured if someone wanted to vote for the same thing, they could just add on to make it 2, etc.
 
Yes I got that; I had put down too many votes (I think I put down 10 votes) then saw you saying five most wanted votes so I removed my 1s so it was just five votes.
 
Yes I got that; I had put down too many votes (I think I put down 10 votes) then saw you saying five most wanted votes so I removed my 1s so it was just five votes.

Well I figured most of us would probably vote for almost everything if given the chance, hence no priority :)
 
Yeah. Who wouldn't want any of those features? ;)
 
Now you're just having fun at my expense :D
It's ok, I don't mind.

I marked my top 5 most-wanted on the spreadsheet. I will wait until tomorrow and then post back with whatever results I have gathered by then.

I'm only kidding A, just a little light humour:rolleyes:

Nigel
 
I'm only kidding A, just a little light humour:rolleyes:

Nigel
I know,
I laugh at myself too, because I definitely tend to make tools for the sake of making other tools etc. I do get around to actually programming every now and then though. :)
 

Users who are viewing this thread

Back
Top Bottom