Grover Park George
My feedback
-
151 votesGrover Park George
supported this idea
·
-
98 votes6 comments · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →Grover Park George
supported this idea
·
-
2 votes
-
4 votesGrover Park George
commented
This is not a help forum.
This is a forum to submit suggestions for enhancements to the MS Access application.
Please take your question to one of the on-line Access help forums dedicated to that purpose.
Good luck.
-
28 votesGrover Park George
supported this idea
·
-
1 voteGrover Park George
commented
This is a design issue in your database, not an application issue. Please visit one of the Access support forums where members offer assistance on specific design issues.
-
1 voteGrover Park George
commented
This is not a support forum. Please visit one of the many Access support forums where members provide assistance on issues such as this.
-
12 votesGrover Park George
commented
Ouch.
-
1 voteGrover Park George
commented
This can be done as a crosstab query. It is a design feature, not an application feature.
Please visit one of the many Access support sites where members offer specific suggestions about handling specific features such as this.
-
6 votesGrover Park George
commented
This can be implemented as a design feature in your specific database. Please visit one of the many Access support sites which have many members dedicated to helping you address specific design requests like this.
-
1 voteGrover Park George
commented
Please visit one of the Access support forums where you can post this as a question and receive guidance from members who can, and do, provide help in implementing such features in your specific database.
-
8 votesGrover Park George
commented
Appending "lost" records back into a table is not at all difficult, if you follow two rules.
To restore any missing AutoNumber, simply include that AutoNumber in an append query that also includes other fields needed to complete the record. In other words, if you know which AutoNumber value was deleted, you can easily put it back this way.
Then, to prevent Access from trying to append new records with previously issued Autonumbers, run a Compact & Repair on that database immediately after appending back the lost record(s).
Obviously, if you have a problem taking the database offline in an unscheduled situation, you'll need to do this during some previously established maintenance window, or in some sort of "emergency" procedure.
In any event, disrupting two decades of established behavior doesn't seem to rise to the level of "enhancement."
-
214 votesGrover Park George
supported this idea
·
-
73 votesGrover Park George
supported this idea
·
-
18 votesGrover Park George
commented
At the risk of throwing fuel on the fire, I want to speculate what might be said about Microsoft if they went about buying up all of the smaller, independent software companies and putting them out of business. I think that is often called "monopolizing" and is generally frowned on.
-
8 votesGrover Park George
supported this idea
·
-
11 votes1 comment · Access (Desktop Application) » External Data Connectivity · Flag idea as inappropriate… · Admin →Grover Park George
supported this idea
·
In addition to the fact that this forum is for suggestions about improving Access, not trouble-shooting assistance, please note that the problem is, in fact, the way wrote the query was originally written. Without the aggregate function Min(), Access MUST select a matching value; the one which coincidentally falls first in the current recordset, not the one you want, but which isn't specified. Min() narrows that down to the one record you want, so that's the proper way to write the query. In other words, not a fault in the query engine.
That said, please take any specific product questions to an appropriate forum run for that purpose.
Good luck with your project.