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.

Sign up for GitHub

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

Jump to bottom

Attribute VB_Name: trouble in and out #72

Open
RossBoylan opened this issue Apr 18, 2018 · 2 comments
Open

Attribute VB_Name: trouble in and out #72

RossBoylan opened this issue Apr 18, 2018 · 2 comments
Labels
bug

Comments

@RossBoylan
Copy link

The .bas files have Attribute VB_Name = "VCS_xxx" as their first line. When I attempted to import a file with such a line (VCS_Query.bas) VBA and the regular Access window hung and I had to kill Access. This was repeatable.

Further, when I file out code with VCS_IE_Functions.VCS_ExportObject acModule, m.name, fpath the resulting file does not have Attribute VB_Name.

When I deleted the first line from VCS_Query.bas I was able to import it. I made similar deletions from the other files awhile ago--I noticed this becaue VCS_Query is new to me (just did a fetch).

VBA version 1643, also identified as Retail 7.0.1643
Access 14.0.7197.5000 (32 bit) part of Office Pro 2010.
Win 7 Ultimate 6.1.7601 SP 1 Build 7601 (64 bit)
Database is an .mdb file, the front end of a split database. Probably created with an earlier version of Access.
@timabell
Copy link
Member

If you can fix it then a PR would be most welcome, thanks for sharing your findings.

@timabell timabell added the bug label Apr 19, 2018
@RossBoylan
Copy link
Author

My understanding is that the .bas files on github were produced from Office 2010, though perhaps not from the VCS_ExportObject method. Since I'm also using Office 2010, the discrepancy seems odd. I don't know what systems operate with Attribute VB_name and which do not. The real problem, of course, is not the output but the way my system gags on the input with attribute VB_Name.

Assuming I could figure out which style the running copy could support (I suppose I could write a test file in the style of VCS_UsingUcs2) I'm not sure how to deal with the problem Once could write code that manually rewrote the start of .bas files in an appropriate way, but that would create a version control problem as changes that consisted only of adding or removing that line would be sprinkled throughout the history. The whole thing seems like a messy kludge.

hangie added a commit to hangie/msaccess-vcs-integration that referenced this issue Mar 22, 2019
@hangie
Remove VB_Name from some modules
1531299 
To fix msaccess-vcs-integration#72 and msaccess-vcs-integration#81.
effjot pushed a commit to effjot/msaccess-vcs-integration that referenced this issue Oct 26, 2020
@joyfullservice
Remove non built-in references on build
753d4df 
In case any non-essential references are added to a new blank database, this function removes them before importing the references from the source specifications. See msaccess-vcs-integration#72 for further details.
effjot pushed a commit to effjot/msaccess-vcs-integration that referenced this issue Oct 26, 2020
@joyfullservice
Use version-specific GUID reference version
ece0208 
Rather than using the lowest targeted version (Access 2010), set the version number to the correct reference version based on the version of Microsoft Access. This should keep the reference version numbers consistent with the expected values. Closes msaccess-vcs-integration#72
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@timabell @RossBoylan