OK that kind of answers my question indirectly.
The point I was making was whether or not having a current connection open to the backend on a concurrent database is a good thing or bad thing.
For instance we have an split application which is used by 100+ users. It is completely...
To be fair I have never considered autonumber to be anything more than an autogenerated unique identifier and I will continue to treat it as such.
To be fair I don't think I have read anything that shows that using an autonumber to uniquely identify the most recent record from a subset in a...
My confusing grows...
So the consensus is that an autonumber is just a great way for Access to organise itself internally and should therefore not be used as a unique identifier for an actual record, rather an autonumber simply uniquely identifies the arbitrary position of any row in table?
So...
I'm getting confused now. Foot note 4 of the linked article seems to suggest it will never change unless under special certain circumstances.
I cannot link the TechNet post due to not having enough posts here and everything I try to put just the link in text fails but if you search for "access...
Thanks for this, yes issues will contain lots of different properties including some of the ones you mention above. My plan was to have basically just the issueID number in the main table, and some static data like who actually raised it in the first place and original target date for...
Thanks that is a different way to do it for sure. Though I am a bit confused by the above statement. I didn't know that a compact would reset the autonumber? It seems crazy that that would happen.
Edit: In fact this seems to only happen on older versions of access:
There is a page on TechNet...
Ok thanks for that, so you are almost saying use the main table as the store for all current information about the issue and then move historical information to the history table.
Certainly makes sense but it again still requires two calls to the backend, one to update the current issue and one...
While I'm on the roll and after posting my first thread just a while ago, I'd thought I'd post another about table structure and holding historical data.
As a rough example of one of the projects I am working on.
The main table will consist of a log of all raised system issues. Say:
issueID...
Hi all I'm new to the boards, so hello.
I've been using Access for about 5 years now to create some quite complex multi-user EUC applications.
Regarding "databinding" in the not .net sense I was always taught that in MS Access you should never directly bind say a combobox or a listbox to a...