Application Development Path

WhizzkidWallace

Registered User.
Local time
Today, 03:57
Joined
Jan 10, 2005
Messages
49
Hi there,

I am developing an application with several sections in a multi-user environment, and want each section to go live as it is complete. I read about splitting into Front-End and Back-End etc, but found problems with speed and reliability when I split it, so I am keeping it all in one file for now.

The problem now is that people are using parts of it already, and this is preventing me doing any further development while others have the database open! I have read somewhere about Database Replication!!

Can anyone give me some clues as to how I can run and develop my app at the same time.

Thanks.
 
database splitting is the best way to go here, An splited db Would outperform a non splited database on a server hands down anytime, anywhere. It will also resolve the problem of what I call fast deployment.

You would have to be sure about the structure of the back end and release a Front end that will change over time as you work on it... You can even easily set up an auto update utility that will warn the users where there is an update available for them to download from the file server...

In short, Go Back end / front End that will solve your problem.

In the years I've used ACCESS, I have never done a single replicating Db, don't think you need it here also.
 
Thanks...but...

Thanks for that. I really do want to go back/front, and can see how much better would be to develop and distribute updated front ends, but when I tried it was very slow and in fact some code just locked the machine every time I ran it.

At the moment I have a Windows 98 network with one XP machine, and the db is stored on a shared folder on the XP machine. When I use the db splitter to move front to w98 machine, and leave the back on the shared XP folder, it is very slow, and hangs when I run a particular report.

Would it really be much quicker on a proper server?
 
Can you develop a separate database apart from what the users are working on, and when you are done, you can roll it out to staff?
 
Yes..but...

Hi,

I can and probably will do that, but it means the data in my version will be out of date, or I have to make notes of every change I make and import new tables/modules/reports etc.

Can anyone advise me of a good hardware/software spec on which to place my back end database to get the fastest result?

Do I need Windows Server......etc

Thanks
 
The speed of your network absolutely affects the responsiveness of the database. One thing you can do to minimize network traffic is to place individual copies of the fe on each user's local drive. The be which is shared is on a network folder.

One thing that seems to slow down the fe/be is if the be is buried way down in a directory tree. Move the be as high up in the directory tree as possible.
 

Users who are viewing this thread

Back
Top Bottom