Search results

Hi Gemma, thanks for your reply. As per my post at #22 I have managed to replicate the error with the most simple database - a single table, single form, no VBA and no queries. So I can safely say that the trigger isn't VBA code. Also, both test computers that I am running it on have entirely...

My development computer is running Windows 10 with Microsoft Access 365 MSO (16.0.13426.20330) 64-bit. The first test computer is running Windows 7 with the Microsoft Access Runtime 2013 32-bit (15.0.4569.1506). The version of Microsoft Office installed on this computer is also 32-bit. The...

Here is the database. The linked table reference will need to be updated in Access prior to running on the runtime version.

Hi all, Hopefully someone out there is still monitoring this thread. I have some additional information that may be of use. I thought I would start fresh and see the absolute minimum features required to trigger this error... the results were pretty crazy. 1. I created a new database with a...

Yes, this is what I thought was the strangest behaviour too. Once I have stepped through the various errors and it becomes stable, it remains stable. Even if I restart the computer. It is only when I delete the database and open up a new copy that it throws the errors again. I will look through...

I have tested the database in runtime on my development computer and it works fine. I have also compiled the code - it threw up one undefined variable. I have fixed this but it doesn't resolve the issue. The SQL query run on start up is very simple - please see below. INSERT INTO tblUserLog (...

Thanks for the suggestion, but the error persists.

Thanks again for the quick reply @isladogs. Just FYI I am only encountering errors when using the Runtime installation of Access. It works fine in the full version. I don't think that I am able to run shift bypass and add in break points in the runtime version, but please correct me if I am...

The error description is "There is no message for this error". The first runtime error (a system error dialog, not one of my error handlers) occurs immediately on opening the database, before any code has been executed. After click OK on this error it continues through the first subs code until...

@isladogs - Thanks for the suggestion but I am not using transactions. The first sub is just a simple QueryDefs execution.

Thanks everyone for the suggestions. So far I have: 1. Added error handlers to all subs 2. Declared Option Explicit in each module 3. Confirmed that both the runtime and Microsoft Office installation are both 32-bit The error message that I receive is "There is no message for this error"...

Thanks for the suggestion. I have re-linked the tables with appropriate path but still no luck. The database backend is currently sitting in the same folder as the front end, on the C drive of the local computer not the server (C:/Users/database_be.accdb). Would I need to use a UNC path in this...

Hi, I'm hoping someone out there might be able to help me with this issue - it is doing my head in! I have developed a database that will be rolled out to multiple users who will only have the Runtime version of Access installed. I have transferred the database to a test computer with the...