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

Run-time error '3075' when checking if table has a data macro #384

Closed
mwolfe02 opened this issue Mar 6, 2023 · 5 comments
Closed

Run-time error '3075' when checking if table has a data macro #384

mwolfe02 opened this issue Mar 6, 2023 · 5 comments

Comments

@mwolfe02
Copy link

mwolfe02 commented Mar 6, 2023

I'm getting the following error message in the clsDbTableDataMacro.IDbComponent_GetAllFromDB function:

image

I seem to be getting the message for every table in my application (or at least the local tables). I think this may have something to do with my environment, otherwise, this would be an issue for others. The problematic code has been in place for three years.

VCS Version: 4.0.7
MS Access Version: Microsoft® Access® for Microsoft 365 MSO (Version 2206 Build 16.0.15330.20260) 64-bit

@mwolfe02
Copy link
Author

mwolfe02 commented Mar 6, 2023

Changing the following line of code from...

strSql = "Not IsNull(LvExtra) and Type = 1 and [Name] = """ & tdf.Name & """"

...to...

strSql = "LvExtra Is Not Null and Type = 1 and [Name] = """ & tdf.Name & """"

...seems to resolve the problem.

joyfullservice added a commit that referenced this issue Mar 6, 2023
A user reported this triggering an error on their system. Using a more simple comparison to test for null. #384
@joyfullservice
Copy link
Owner

That is interesting... It almost seems like the type of error you would get if there was a compile issue elsewhere in the code. 🤔

@joyfullservice
Copy link
Owner

@mwolfe02 - FYI, I am not sure if you are already doing this, but you can clone and build the dev branch to pull in all the latest updates. 😄 I also went ahead and pushed out an updated beta release since we have added some more substantial features and fixes since the last one. Let me know how it works on v4.0.9.

@mwolfe02
Copy link
Author

mwolfe02 commented Mar 7, 2023

v4.0.9 resolved the issue. I'll have to look into cloning and building from dev. I wasn't aware of that. Thanks!

@mwolfe02 mwolfe02 closed this as completed Mar 7, 2023
@joyfullservice
Copy link
Owner

Cloning and building from source is really easy. I use GitHub Desktop, but any other git client works fine too. The first time you do it, you won't have the binary in the folder, but you can just drop a copy (any version) into the root folder of the project.

  1. Close all open instances of Access, then double-click the Version Control.accda file to open the add-in. Hit esc or click the x to close the install window.
  2. Click Build from Source on the ribbon toolbar, and click OK on the confirmation.
  3. After the build completes, close the database.
  4. Open the newly built add-in file, and this time proceed with the install. The add-in will close automatically when complete.

And that's it! You now have the very latest version of the add-in installed. 👍 Anytime you want to pull in the latest changes, just run through the four steps above. 😄 (I love version control with Microsoft Access!)

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