Search results

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...

Did the code in your project compile after deselecting this reference? I didn't see where you mention completing that step? I, too, am curious about the reason for using the Microsoft Jeft and Replications Objects Library with that version. It appears to be a JET DLL, and therefore dating back...

True, but there are other backup solutions available, both free and paid. For example, here are two selected at random, with no recommendation implied: https://www.sqlbackupmaster.com/support/sqlexpressscheduledbackup https://sqlbackupandftp.com/

Please note that the proposed solution, which is the appropriate choice, is NOT to store the documents and images internally. The appropriate approach is to store them externally, in a shared folder, and only store the path to the image or document in a field in a table in the database.

I have created PowerApps apps that run on a smart phone. No one, and I mean no one, wanted to use them. On a tablet sized screen, though, they are usable. This definitely falls under the category, "Just because you can, doesn't mean you should even try."

"The prospect also wants remote users to use portable devices to capture and save images, scan barcodes, and print labels..." PowerApps does that well. See the videos in this series on YouTube, such as this one on scanning barcodes for Northwind Developer. I also take photos of book covers...

The calculations are right there in your screenshot. Right below the Default Formatting which applies Yellow, the next conditional format says, "Condition 1 Field Value Is greater than or equal to 0" then Green is applied.