Access build stopped workiing, form problem errors 2473 and 6. Cannot access form to fix

[rmcbain]

Apologies in advance I am not sure in which category to post this problem. Our business has been using a point of sale system developed in Access 2016 since circa 2010. Amazingly this .mde build has been working extremely well for all these years… Until now. I am not very familiar with Access and the developer can no longer be found.

Overview of the working environment. We are running Access 2017 on Windows 7. I believe all files were written in Access 2016 as the database file is .mda.

The current problem is we can no longer create new job tickets. Reviewing the error logs the problem seemed to have started:


10/25/2024 5:25:01 PM, Form_ErrorFormSalesOrders, Application-defined or object-defined error, 2473 (error code).
Since this event we now get the following error when trying to create a new order.
10/25/2024 5:25:10 PM, NewSalesOrderNumber, modVariables, Overflow, 6 (error code). Since these errors started the software does not automatically compact and rebuild when opened for the first time each day. I have rebuilt a copy of the .mda file but that did not solve the issue.


Fortunately we are able to do all functions except write new orders.

Where I am stuck is I cannot access any of the forms. My basic research indicates that I should be able to inspect and edit the forms through the .mda file. I can view all the tables in the .mda file but cannot find the forms.

This issue is critical to running our business and I realize I am in over my head. I don't know if it is appropriate to try to hire someone through this forum, but this is probably what I need to do.

[mike60smart]

Hi
Are you able to upload a copy of the database?

[Welshgasman]

I am going to suspect that a field is too small to hold a number, as it has been running for so long.
AFAIK .mdx is pre 2007 db type.

[mike60smart]

Hi
Do you have access to the original Mdb File?

[Bulzie]

Have you tried to manually compact/repair the FE file? You said it is file ext of .mda? What is the backend data, SQL or Access? I am not familiar with .mda, others might be able to help with that. If you cannot add new records, might be space issue or number limit, etc.

[Welshgasman]

https://answers.microsoft.com/en-us/...1-8b10b979bd03

[Micron]

.mda is an add-in file, no?
.mde is the "compiled" version of .mdb; accde the compiled version of accdb. It is odd that you say the file was developed in version 2016 yet is .mde

Application-defined or object-defined error, 2473

Such errors out of the blue are often caused by
a) badly written code that breaks after an update or
b) an update introduces a bug. Seems to be a common thing lately. If you just updated, consider trying to roll back and see if the issue goes away.

Error 6 may be due to your SO number being defined as integer in table design and you hit the limit (32767).
Aside from what I suggested re rollback, I think you'd need to fix the mdb file and remake an mda out of that. Backup these files ASAP and don't alter their design - alter the copies.

[rmcbain]

Hi
Do you have access to the original Mdb File?

I doubt it I have backups from 2022 and 2018. I am new to this forum.

[rmcbain]

Have you tried to manually compact/repair the FE file? You said it is file ext of .mda? What is the backend data, SQL or Access? I am not familiar with .mda, others might be able to help with that. If you cannot add new records, might be space issue or number limit, etc.

I cannot find an FE file. I hired someone in Europe to build this point of sale system. I don't how to answer if the backend data is SQL or Access. This is a very old build which is way the database is .mda

[rmcbain]

.mda is an add-in file, no?
.mde is the "compiled" version of .mdb; accde the compiled version of accdb. It is odd that you say the file was developed in version 2016 yet is .mde
Such errors out of the blue are often caused by
a) badly written code that breaks after an update or
b) an update introduces a bug. Seems to be a common thing lately. If you just updated, consider trying to roll back and see if the issue goes away.

Error 6 may be due to your SO number being defined as integer in table design and you hit the limit (32767).
Aside from what I suggested re rollback, I think you'd need to fix the mdb file and remake an mda out of that. Backup these files ASAP and don't alter their design - alter the copies.

I actually can't remember when this project was started. I checked all my email correspondence with the developer and I got back to 2010. I think the problem might be "Error 6 may be due to your SO number being defined as integer in table design and you hit the limit (32767)". The start number was 1001 (without verifying)

[rmcbain]

Hi
Are you able to upload a copy of the database?

I could upload a copy of the database, but I am concerned because the database has 1000s of client records

[mike60smart]

Hi
You can PM me if you are concerned about uploading to the forum.

[rmcbain]

The files are backed up in multiply locations. I don't think this is rollback situation as we saw the fail real time. I have viewed the TblOptions and the orderNoStarting is 1001. If the table design has hit the limit what is the next step

[Welshgasman]

I could upload a copy of the database, but I am concerned because the database has 1000s of client records

Take a copy and run this on the copy
Randomize Data

[rmcbain]

Thanks I used the randomizer. Now how to upload the file to this thread?