search

rubberduck-vba / Rubberduck

Every programmer needs a rubberduck. COM add-in for the VBA & VB6 IDE (VBE).
https://rubberduckvba.com
GNU General Public License v3.0
1.92k stars 302 forks source link

Was looking up source control for Access 2016 and was directed to RubberDuckvba.com/sourcecontrol #5333

Closed RSquared64 closed 4 years ago

RSquared64 commented 4 years ago

There is at least 1 website pointing to RubberDuck as being able to provide Source Control for Access.

On YOUR sites of course there is no listing of being able to provide source code control.

At the very least, it would be an awesome addition to RubberDuck.

Thanks

rubberduck203 commented 4 years ago

At one point, years ago now, there was a git interface in RD. Unfortunately, it was highly experimental and I didn’t have the time to get it working smoothly so we removed it.

The best option at the moment is to use the export/import feature to get the code on to the file system so you can use whichever source control system you like.

A9G-Data-Droid commented 4 years ago

For Access we would need more than just VBA. There is a plugin that can dump access object data to text files so they can be properly controlled:

https://github.com/joyfullservice/msaccess-vcs-integration

bclothier commented 4 years ago

Yep!

Given that Rubberduck's scope is a VBIDE add-in, I think it's safe to say that Access, which AFAIK is the only host to ever have had support for source control of its documents, is best served by specialized Access add-ins such as the one linked or various commercial offerings. For that reason, I would argue that such control would be beyond Rubberduck's scope.

If anyone happened to find out a truly host-agnostic solution to control the documents then we might be able to talk about that, but I just don't see it happening. Hopes that he won't have to eat a pie of crows one day for having said that.

rubberduck203 commented 4 years ago

@retailcoder I’m going to go ahead and close this. I’m agreed that an Access specific (table/query defs, etc.) are completely out of scope and that we’d accept a PR from a champion/maintainer of a VBA source control solution, but there’s no sense in leaving this issue open. When/if such a maintainer comes along, I’m sure they’ll open a new issue.

@RSquared64 thank you very much for the feature request and being a RD user. I’m very sorry to close this. It still breaks my heart that I failed to deliver a working source control solution for RD.