This site is for offering suggestion relating to MS Access Databases. Please post your suggestion in a more appropriate forum, I'm assuming PowerPoint.
I seriously don't expect them to be resolved.
MS has already proven this site does not do what they said it would do by ignoring highly voted items and completing suggestions with next to no votes.
MS will never be in a position to say they were never told about the issues as long as we post them.
You can add control dynamically through VBA using the CreateControl Method (https://msdn.microsoft.com/en-us/library/office/aa221167(v=office.11).aspx). Does this not do what you need?
I agree with the suggestion, but have no votes left.
Here's a function I found a while back to disable it throughout all the forms of the database.
On Error GoTo Error_Handler
Dim ctl As control
Dim frm As AccessObject
For Each frm In CurrentProject.AllForms
DoCmd.OpenForm frm.Name, acDesign
For Each ctl In Forms(frm.Name).Form.Controls
Select Case ctl.ControlType
ctl.ShowDatePicker = 0
DoCmd.Close acForm, frm.Name, acSaveYes
On Error Resume Next
Set frm = Nothing
LogError Err.Number, Err.Description, _
sModName & "/DisableDatePicker", _
I long ago ditched the status bar (far too small that users simply don't even notice it) and started to use a form which I control the visibility of a series of texboxes (colored background) which simulate a progress bar very nicely. I open it modal/pop-up while processing various things and the users can see the progress and can't miss it.
All of this to say, I think Alan is correct that there are some very good alternative already out there and they're probably better than any MS will put forth.
It doesn't hurt to make the request, but don't let that stop you right now from implementing a solution.
A Quick Google finds many solutions:
+1 I'd vote but no votes left.
Look at the post and samples provided by Daniel Pineault found at: http://www.utteraccess.com/forum/index.php?showtopic=1992179&st=0&p=2276028&#entry2276028
I agree with Mark. Since PK have no meaning, the fact that they jump should have no importance.
Performing a C&R resets them to the greatest taken number, so you could always do that to get back into sequence.
You seem to have a specific scenario in which you are reliant on the values of autonumber which seems wrong. Why not create your own numeric field then you can populate it as you see fit with whatever sequence you wish.
Valid point George.
Same idea as https://access.uservoice.com/forums/319956-access-desktop/suggestions/14833125-buy-fishers-find-and-replace-and-incorporate-it . Make real suggestions for features, rather than buy this, ... Say we need a better Find and Replace Utility that work throughout the entire databse, .... Say, improve VBE/VBA to enable better error reporting to automatically include Module Name, Procedure Name, Line Number instead of buy this....
Considering the level of engagement MS has put forth on this site's suggestions, I wouldn't hold my breath on this one!
"Storing the path would NOT work on a different machine" why not? Create a subdirectory in the db directory to house your files and copy the whole thing. I VBA you can easily reference such files.
Another alternative is to house them in a table and then at runtime extract them locally to use them as you need.
Either way, there truly is no problem here.
+1 here, but out of votes!!! If you want to set default value on fields, then you should give us the ability to define what the default values will be, but 0 would not be one in my books.
You can already incorporate various HTML editors directly through the native webbrowser control.
A properly designed database does not fluctuate in size too much. Normally such fluctuations and bloating are indication of errors in design/usage, such as the use of temporary tables, repetitive insertions/deletions, the use of attachment data types, etc.
Please provide more information regarding the strange problems you are experiencing.
At the very least report them in plain English.
This is what a library database is useful for. You place your procedures in it and link it like a reference and then you have only one place to make changes, push out an update of your library and all your dbs are updated and in synch.
A lot, if not all, of this can already be done using proper table design, validation rules, input masks, formats.
The team has reviewed this request and seems like different people are commenting about different things.
@Nigel, can you please elaborate what you meant in this request?
I would vote, but am out of votes, beyond which, based on what we have seen on this site (number of submitted suggestions vs Not Planned vs Planned/Done, I've basically given up on this site. It was obviously another PR game played by MS and it worked! People are talking and MS is simply not listening.
But you aren't wrong for asking for a proper solution rather than a workaround!
Just build your own Tab controls, a series of Label, command buttons, ... They all work fine and then you use their click event to control what is visible. Very easy to implement and works flawlessly.