Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 94 "Incorrect use of Null" in Function "IDbComponent_DbObject" #408

Closed
monheimx9 opened this issue Jul 2, 2023 · 5 comments
Closed

Comments

@monheimx9
Copy link

Dear joyfullservice

While exporting all sources

In the class "clsDbSharedImage"
In the Function "IDbComponent_DbObject"
Error 94 on the line:
m_Extension = m_Rst!Extension
"Incorrect use of Null"

Tested on version v3.4.23 and tried on v4.0.13-beta as well
(I took some long programming vacations, the add-in was working perfectly before)
Access Version 2306 Build 16.0.16529.20100 (64Bits)

Here you can find a screenshot of the Immediate Debug Window
Capture d’écran 2023-07-02 203716
"<Opération non autorisée pour ce type d'objet>" means "Operation not authorized for this object type"
"Vrai" means "True"
"Faux" means "False"
"Opération non valide" means "Operation not valid"
Translated from French

If I can provide you additional informations feel free to ask

Otherwise I want to thank you for this amazing addin, I used it a lot last year and provided me great help in my workflow
Cheers

@joyfullservice
Copy link
Owner

Thanks for reporting this! I have wrapped the field reference in the Nz() function to ensure that we are assigning a string value to m_Extension.

joyfullservice added a commit that referenced this issue Jul 5, 2023
Best practice is to never assume a field will contain a string value, but use the Nz function to handle the possibility of null values. Fixes #408
@monheimx9
Copy link
Author

Thank you for your answer, I've made the change on my side as well
But might check my comment here f8d1f22#r120797607
I think there is a typo

Wish you a nice day :)

@monheimx9
Copy link
Author

Sorry, did not see 6052299
Thus my previous comment is irrelevant

@joyfullservice
Copy link
Owner

Yes, you are correct. I had some other refactoring I was doing in other commits around the same time. 😄 I am hoping to build an updated beta version in the next few days, which should include this and other fixes.

@joyfullservice
Copy link
Owner

I believe this has been resolved now. Closing out as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants