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

Feature: Select Build Version #224

Closed
hecon5 opened this issue May 18, 2021 · 2 comments
Closed

Feature: Select Build Version #224

hecon5 opened this issue May 18, 2021 · 2 comments

Comments

@hecon5
Copy link
Contributor

hecon5 commented May 18, 2021

From @cwuensch's comment:
If a newly created database would use the default format configured in MS Access.
This way, you could convert an "old" *.mdb-file into new *.accdb format.
Also, you could stick with legacy formats, when you configure Access respectively.
Originally posted by @cwuensch in #217 (comment)

@hecon5
Copy link
Contributor Author

hecon5 commented May 18, 2021

In my mind, I think this may be easiest to handle by allowing either building into the version of file that was exported OR build into the Default Format for Blank Database (under options) setting.

In any regard, if you had code for a Access 2003 legacy .mdb and have Access 16, you won't be able to back-compile to that file version, but you may want to compile to be backwards compatible with, say Access 2010.

Perhaps this could be a simple checkbox under Build to use either the "Use Default file Format for Blank Database" or into the exported database's format. If the Access version is too "high" to compile into a legacy version, then use whatever the default is.

Personally, I think it should default to use the "Default file format for Blank Database" setting to ensure building works the same way as it did before #217.

image

@hecon5 hecon5 changed the title New Feature: Select Build Version Feature: Select Build Version Feb 24, 2022
@hecon5
Copy link
Contributor Author

hecon5 commented Oct 23, 2023

After re-thinking this and how V4.x works, I think the build version should remain as is selected in the database itself, and VCS should just rebuild as stated. This keeps the scope consistent with other design choices in VCS.

@hecon5 hecon5 closed this as completed Oct 23, 2023
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

1 participant