Access Runtime Limitations?

[kstevens]

I know that I cant do alot of things with runtime that i can do with regular, and i know that one of those limitations is writing to a runtime table from another database, but does that also mean that i cant write from a runtime database, to one that is not runtime.

The scenario is:

I am using a runtime database (we will call it main) that houses the records i want, when a button is pressed i want it to append a table in another database (sub) that is not runtime.

This works for testing when I test the main database if the main is *.accdb, but i get a runtime error when i change the extension back to *.accdr.

If it doesnt work, and this is one of the limitations, then please just tell me, lol. I will have to figure out something else. Thanks in advance.

[nico5038]

Make sure the reference to the database is also having the same extension.
Once set for *.accdb, it won't work for *.accdr and vise versa.
When you need both, a check on the .mdb name is needed.

As far as I know there's no difference between updating a runtime or "normal" Access database.

Nic;o)

[kstevens]

I shouldnt admit this.... but the query i am running is qryUpdateMatlAndCert... the button is pointing to aryUpdateMatlAndCert, hmmm pesky little finger type an "a" instead of a "q". Sorry for the problem, and thanks for the response, but i did think there were problems writing to a runtime....i will test and see. Thanks again.

[nico5038]

No problem, but the different references will be needed when different databases are used :-)

Nic;o)