I have a split database with the backend on our server here at work that has several users in it all day. Since I'm still developing it while others are using it I have to announce to everyone to get out of the database to go in and add a field to a table or make any changes to the table. Was just wondering if there is a better way to do this so the users don't have to close down every time I want to change something on the backend. They get pretty frustrated when I ask them to get out sometime several times a day.
Backend table editing question
- Thread starter zgray
- Start date
Yea I do the same thing. I have a copy of the frontend and backend on my computer where I do all my testing and developing. But when I want the changes to go live on the live backend I have to ask for everyone to get out, make the changes, and then tell everyone to get back in. I cant copy my test backend to the server.
- Local time
- Today, 17:03
- Joined
- Jan 23, 2006
- Messages
- 15,572
Can you not schedule your changes for specific time? If users knew changes were done/made on the 15th of the month for example, then it would seem everyone could work with that and issues minimized. Sounds like you're changes happen a little too sporadically. Do you have a development-- acceptance-- production approach?
Gibraltar102
New member
- Local time
- Today, 23:03
- Joined
- Mar 10, 2014
- Messages
- 3
The solution for you may be a little like this...
Retain your developers BE and FE on your development pc.
Copy your updated FE to a distribution folder on the server.
Each user launches your application from their local drive.
A "launch" batch file can copy the FE from the distribution folder on the server to their machine at the time of launch, thus ensuring they are always using the latest FE that you have copied to the distribution folder.
Although this might seem a little basic. It works. You never disturb the users when you need to update users FE's, and you can fully test your changes before publishing to the distribution FE folder in the server.
You can even publish a part complete form, with the opportunity to place an "under construction" graphic on the form.
Alan, Gibraltar
Retain your developers BE and FE on your development pc.
Copy your updated FE to a distribution folder on the server.
Each user launches your application from their local drive.
A "launch" batch file can copy the FE from the distribution folder on the server to their machine at the time of launch, thus ensuring they are always using the latest FE that you have copied to the distribution folder.
Although this might seem a little basic. It works. You never disturb the users when you need to update users FE's, and you can fully test your changes before publishing to the distribution FE folder in the server.
You can even publish a part complete form, with the opportunity to place an "under construction" graphic on the form.
Alan, Gibraltar
