Distributed Dbase

[coolcatkelso]

Hiya guys

My Dbase is almost ready now for Distribution, but just a question...

Is there a simple way to update this Dbase?

The current version is 1, lets say there was a simple spelling mistake or something and the customer asked me to change it... Apart from giving him a whole new version, is there no way I could just update the accde?

I don't think that splitting the Dbase would help, would it?

If the Cmr has been using the Dbase for a while and has stored alot of information and I give him a new version etc then he would lose all that info?

Any ideas?
________
Box Vaporizer

 

[GaryPanic]

spliting the d/base put's the data in one place and the processor in another
anychanges therefore should be on the processor - no change to the data)

Spliting db should be seen as the norm - better performance
(well that's my view anyway)

 

[dbDamo]

The Database should be split anyway - This way any information stored in the tables would be safe, and you would only have to distribute a new front end.

 

[Lightwave]

Another vote for splitting the database - you can then make changes to the interface and provided you haven't made any changes that require changes in the structure of the data you can simply change the front end.

The advantage being any work your colleagues have been doing on the database non of the material data is lost.

 

[gemma-the-husky]

but you would have to redistribute the dbs to change anything unless

.... you find some way (inefficient generally - but probably used to privide eg variable language options) to populate stuff like this from a support file, or table - in which case you could just update the table

even if you use a main dbs, and support code libraries (which is tricky to implement) you would still have to release modfiied libraries