FishGuy
Jan 12th, 2006, 10:57 AM
On behalf of our small IT team Im looking to develop a kind of source control application, to solve the problems of the given scenario.
In our company we have many small applications which although use SQL Server for a backend still use MS Access for the Interface. It is not feasible to rewrite these apps but as the development team is growing and different people a constantly making changes to the apps we need someway to control the changes.
I would like to make it so a user is forced to ineffect check out the mdb's when they work on them, then other users can see whether work is in progress and by whom along with details of work history.
Any Ideas of how to actually implement this, I would be grateful.
In our company we have many small applications which although use SQL Server for a backend still use MS Access for the Interface. It is not feasible to rewrite these apps but as the development team is growing and different people a constantly making changes to the apps we need someway to control the changes.
I would like to make it so a user is forced to ineffect check out the mdb's when they work on them, then other users can see whether work is in progress and by whom along with details of work history.
Any Ideas of how to actually implement this, I would be grateful.