Search results

Winner.

I don't have direct contact with the MS Access team any longer. With all of the other priorities already on their plate, I don't think I'd try to insert this particular initiative into their plans anyway. I'm also skeptical that adding such a guide would make all that much difference anyway...

As I said, there have been many such attempts to provide guidelines for designing and building normalized relational databases, some brilliant, some less so. I bet a search right here at AWF would turn up more than one. The problem, as I see it, isn't a lack of written guides. The problem is...

A guide? Not a document as such. That's actually beyond the scope of the charter for Microsoft templates in general. We went to some trouble to provide a consistent Relationship Diagram for the Developer version because otherwise it's generated in the muddled state typical of newly created...

What theDBGuy was referring to: https://learn.microsoft.com/en-us/sql/tools/bcp-utility?view=sql-server-ver17&tabs=windows

Well, the crash is locking the database, so it makes sense that all are impacted the same. I qualified my comment about the problem by saying "if" it is caused by shutdown of a laptop. So that's not a definitive consideration. Rather, if a process is being interrupted during a write operation...

Ah, if the problem is that undisciplined users shut down their laptop without first closing any open applications on it, the only solution I can think of is a bigger stick, figuratively, of course. A mandatory training session could help. Passive aggressive behavior, unfortunately, is hard to...

Reading previous responses along with this observation, I'd like to call your attention to what appears to be the primary cause of the problem. "Crashing" the database application. That will invariably leave a dangling lock file and can cause other problems for your users. Your strategy needs...

RegExp is now on this computer. M365 is 32 bit.

Getting V1 produced by an AI LLM is fast. Bug-fixing V1, V2, V3, V4, and V5? No so fast.

Given the fact that Access 2010 is long out of support, and that ADPs have been deprecated for a few years, and that the faulting dll is related to JET 4.0, which has been supplanted by ACE, I doubt there's a high likelihood of a fix.

Is there supposed to be a link here?

A long time ago, around 2011 or 2012, we did some work that involved both Project and Access. I can't remember doing much automation with Project, though.

I converted the Extended Date Time fields in one test table to Date/Time. That table imported. Not something I'd do on a regular basis, but as a one time project, it's doable.

As a test, I imported every object from an accdb into an mdb, except for tables that did not qualify due to fields with Extended Date Time datatype. Several plain vanilla tables did import. As Colin says, as long as you are aware of and deal with pertinent issues such as modifying datatypes, it...

Good points. I stopped with just creating tables that could be imported/exported. In any event, without knowing why the OP needs to do this, it's hard to offer very specific suggestions anyway.

While it true that you can't export tables with newer features, such as support for Large numbers and Date Time Extended, from an accdb to an mdb, it is also true that plain vanilla tables CAN be exported from an accdb to an mdb, as I just did. By modifying your tables to avoid such conflicts...

Let me rephrase. You could use Access 2010 (or newer) to create an empty mdb. Then you could try to import the objects from the accdb into the mdb using Access 2010 (or newer). Also, I should acknowledge that I did interpret this phrase, "...transform my database to older type" and the post...

Gasman beat me to the "WHY?" question. What problem would be solved by downgrading the accdb to an mdb?

You could create and mdb and try to import all of the objects from this accdb into it.