Going to add support for these DB's too whilst I am decoding the Music DB.

Mark

For version 4 with the mysql sync, is this going to be in a number of months then? I'm working on my own collecting data for books, and I'm trying to decide the best way to get the data into my database, whether to put into the mysql db directly, macro scripting, or exporting to csv then importing into kollection.

Yes, this was always going to be the case because of the code that requires implementing so that the MySQL adheres to DB constraints. This requires MySQL functions, procedures and foreign key constraints to be written and tested. I have done some of this already and it is looking good Also, the syncing part (from the client KollectiON side) will need coding and testing from scratch.

The reason for choosing to add Game/Comic/MP3/Photo support to KollectiON is that from experience of writing KollectiON it is a lot more time consuming and error prone if I add them at a later date and then try to tweak parts of code to incorporate the new DB format. For example, if I continue to just re-write the MySQL section for just Move/Book/Music DB's and then later add, say Game DB support for MySQL, I have to modify the MySQL code to incorporate the new Game DB. Eventually the code can get messy and hard to maintain.

Do you think you can wait? because your input is valuable to this project.

Mark

Yes, of course I can wait No matter what way I do it, I'm still going to be using Kollection. I just have to decide whether I want to macro or use csv now.

When you say you are adding support for those DBs what exactly do you mean? Is it gonna be like with Movie Collector where you have all kinds of scripts that you can updated you DB entries with or will it be more like the Book Collector support where you can just open up the DB with Kollection?

Initally you will be able to export all 7 Collectorz formats to a MySQL Database.

BTW, you are not correct when it come to Book Collector support in KollectiON; currently you can Import CSV, Export, image rename and image cleanup to MySQL for Book Collector databases.

Mark

I did not mean to sound crass. I dont really use the Import or export capabilities of Kollection or Collectorz much if at all. What I was refering to was the update capability you get with your movie DB when you open it with Kollection. I would love that capability with all the Collectorz DB but I know that is a lot a work.

Yes, others have asked for this and it is certainly something on my list. Realistically though I do not see it happening this year as I have a lot to do. Bear in mind that it took a year to code and get it working reasonalbly well for Movies.

My main focus this year is on MySQL with sync capabilities for all 7 products and also XML import for 7 too. Plus any bugs / code maintenance in parallel.

Regards Mark

Damn, I did not really expect that fast of a reply. I went to get a cup of coffee and by the time I got back I had a reply. Thats service!

Anyways, I currently work in the computer science field and was never good at the Programming/Web Programming aspect of it. I could write you a hell of a dos batch file though I digress, the point of the above statement is I know how time consuming MYSQL can be and I thank you for time you put in to give us access through Kollection. I have not used Kollection for long but it is such a great tool to update my movies. Thanks again and keep up the dilligent work