Search results

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.

That works on Win10 as well.

This is how we display in NW Developer the Qty to Reorder calculation Mark describes.

Exactly. One more time, though, there is an example all ready for you to study and explore. It's in an Access template called Northwind Developer. Because some people have reported problems instantiating the database from the template, I put a reinstantiated accdb on my website. You can...

That is the Allen Browne method we keep suggesting as a model to follow. See Northwind Developer for a more recent implementation of it.

As you've been advised before in this discussion, is risky to create and store calculated values in tables. Adding another such calculation in the form of a qtyonorder field is a step further down that path. What happens is that stored calculations then freeze in place values that can change...