forked from ArminBra/msaccess-vcs-integration
-
-
Notifications
You must be signed in to change notification settings - Fork 78
Escaping/unescaping of table data - backslashes #83
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
Labels
Comments
would you be able to turn this into a pull request? more likely to get included that way |
I don't really know how to do that. I will take this as an opportunity to learn, but it's rather low on my priority list at the moment. |
You can leave the issue open, it's a valid problem |
fixed in #93 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My Project includes a table that holds pathnames and one of those happens to look like "...db\test...".
When exporting this the backslash rightly gets escaped to a double backslash. But when importing the data back in the unescaping breaks it by reading the remaining "\t" as a tab and converting that.
I have added a very slightly cleverer unescape routine to my copy which fixes the problem for me.
Find attached VCS_Table.bas which calls VCS_EscapeString and VCS_UnescapeString respectively instead of the simple string replacement. And VCS_IE_Functions.bas which implements the pair near the bottom.
VBA is not my first language, so I do not claim any nice properties of this implementation other than that it works for me.
Thank you very much for your work, it has made developing with MS-Access much more bearable for me :-).
Marian
The text was updated successfully, but these errors were encountered: