Runtime error 380

[Ncfire]

I use a crash reporting program at work that uses Microsoft Access databases on the back end to store data from forms that are filled out. There are numerous tables in that access database that are used.

The other day there was an update pushed out to that reporting program, and admittedly I missed a couple versions in between, but our tech people said there should be no issues. The update went fine, until I log in using the username/password(which is also stored on that MS Access database). When I try to log in and the program starts loading, I get the following error:



After talking with our tech people who had me restart and tried to go to the backup database which is automatically created, I still get the error. Their only solution then was to drop a blank database that works fine.

I'm looking for advice on tracking down what may be causing this error. I opened the old database and started manually copying tables over to the new one. Some tables will work but I'm losing a good amount of data in the process which will not copy over due to 'key errors'. I have gotten the program to open using some tables but if I copy everything the error replicates itself. I'm not too awfully familiar with Access so I haven't pushed my limits. I have plenty of backup copies so if I stumble I can just delete it. I'd love to attach the database but it contains personal information.



There's 8 years worth of reports in this database that I would surely love to be able to hold on to. Thank you!


EDIT: I've located the table that causes the error to be thrown when I move the data over to the new database, I'm just not sure where to look to know whats causing it. 2100 entries in it.

[Welshgasman]

Database should be split?
So once you get it working again, split the database.

Your data should be safe then, your code, well that is another matter.

That appears to be a user generated error, so we would have NO CLUE as to what is causing it.

You would likely need to upload the DB or supply a link to it if too big.
To protect any data, you can use this function on a COPY of the DB that has the error.
Randomize Data

You could however try the Shift Bypass option. Hold the shift key down whilst starting the DB, then walk you code line by line or with breakpoints.

[Ncfire]

It's not my code, I didn't write the program. The program uses the tables on that database to store records, it doesn't appear to be any code on the database itself when I open it. I'll check out the randomize data and see if I can get it uploaded, its about 15mb.

[Ncfire]

If there is any record at all in this one table, it throws the error. I'm wondering if there's just an issue with this new update for the reporting program.

[Welshgasman]

Well that error message it telling you exactly where that error is occurring?
So whoever created this should be looking there.

Obviously not tested very well.

[Ncfire]

So are we confident this is being caused by the new update instead of the access database?

[Welshgasman]

It is being caused where that error message is showing you.
If it has been working for years and then falls over, then I would suspect an update. It could also be data, but as the error is invalid property, that tells me someone did not test thoroughly before issuing the update.

So I would put money on the update. That problem could have been in versions you never updated to as well.

[CJ_London]

you say it is using access back end - so what is the front end? and you say an update was pushed out to the reporting program - what was the update about? who pushed it? someone in your organisation or an outside vendor?

An invalid property error is not (or should not) referencing a data issue but a property issue. Properties in the case of table fields are things like the type of field (text/integer/date etc), formats (how the data is be displayed), whether nulls are allowed, whether it is indexed etc. and they will vary depending on the type of field. For example a number field will have a decimal places property that does not exist for dates and text. Further some properties are not created until they are actually required.

'invalid property value' implies perhaps the property exists but has not been completed or completed incorrectly.

The message actually seems to imply the problem is occurring in your frmMain open, load or current event. Not clear whether FillPanel2 or MaskEdBox is a sub or function called by one of those events but the property error may be referring to control, which like table fields have properties such as controlsource (perhaps spelt incorrectly).

Either way, I would have thought whoever provided your eCrash application should be able to diagnose the problem - that is what these types of applications are supposed to do

[Ncfire]

You’re were on the right track here. After hours of it driving me crazy I solved it.

A couple weeks ago during a training event the instructor had us change the date format on our PCs. I noticed on another application when filling in a date field it kept throwing an error whenever I attempted to input data into any field relating to dates. The light bulb finally went off here and I changed the date format in windows back to default. After a restart both applications began to work correctly.

Sorry I didn’t have much more information to provide earlier today, but I’m not familiar with the workings of that program and had been incorrectly informed that the database had to be corrupted.

Thanks for the help.

[Welshgasman]

I would let that instructor know, to put things back as he found them after the course.

[Ncfire]

I would let that instructor know, to put things back as he found them after the course.

Well I didn’t think much of it because I never would have thought changing a date format from 07/04/2024 to 04-Jul-24 would have caused so much havoc with my programs.

Learn something new everyday!

[orange]

Glad you have it resolved.