Forum Replies Created
WintermuteParticipantOctober 1, 2009 at 5:41 amPost count: 12
The main reason it gives me a much cleaner desktop.
It also allows me to keep all my business in a files in a cleaner hiarchy. I have the one default tabble for all my property grouped there, and then under the main heading I can create all the subtabbles.
It is a way for me to keep everything tightly organized.WintermuteParticipantSeptember 17, 2009 at 9:19 amPost count: 12
– what kind of syncing would you expect?
I would like the databases to be able to update each other, and to move the associated files as well. That way I have a mirror copy on each machine.
– how do you expect it to work?
Here is the gotcha. Most examples I have worked on in the past do it through a client server model. I think that could be an option for the business side, but I am not sure if it would be the best method for the other versions. The old one I used you could work offline, and then it would sync up with the main database. The only concern would be if multiple people had the same file, but you can have an option for check out.
The key is the database, and the files would have to be kept in sync for it to work correctly. You could either do a "server" side database with an offline option, or two seperate databases that try to sync each other when connected.
Are you using the access engine for the backend DB?
Already bought the business version. 😉WintermuteParticipantAugust 14, 2009 at 7:57 amPost count: 12
"BARIO" wrote: Hello Wintermute and welcome to the forum 🙂
– We actually heard many requests of a version control system, but people seem to have pretty different ideas about how it should work… what is it that you have in mind? What kind of workflow?
I think the best way to implement it would be to have a view that shows the different versions. That way you only seem them when you are looking for them.
– as for saving the db: the db is automatically saved every 5 minutes and when you close Tabbles. Tabbles keeps a backup of the database, plus you there is a built-in feature to backup and restore the db. Do you really think you need more than that?
My best regards,
I am talking about actually storing the data in the DB. That way your word file, etc is stored as an object in the database. Then tabbles becomes the true system for storing all objects in the database. When you back up data then you would have one central file to back up. It also means it is harder to lose the files since they are in one place. Right now you can break a link by just moving the file in tabbles.