|
Welcome, Guest. Please Login or Register.
Nov 20th, 2008, 12:46pm
Author |
Topic: Migration FAQ (Read 1614 times) |
|
miclev
Newbie
I love YaBB 1G - SP1!
Posts: 3
|
 |
Migration FAQ
on: Jun 21st, 2006, 1:20pm |
Quote | Modify
|
I think that some information is missing in the FAQ regarding Version 6 migration process. Some of the following should be present.
When is the version 6 GA is expected? I think I saw a comment in one of the FAQ that version 6 would keep the Beta suffix. I’m I right or is it a wrong interpretation?
Could a version 5 database be opened directly using version 6 without loss of information or should an Export – Import process be used instead?
Should version 5 be removed before installing version 6 or can it be installed over? Is the registration code preserved if installing over or must it be entered again?
Could version 5 registration code be used with version 6 or must a new one be requested.
Will there be an « upgrade » fee for current users or will it be free when GA of version 6 be out?
My first impressions of version 6 are pretty good in regard of classical information. During my tests I did opened my database and it did not complain but I think that some data « disappeared » in the conductor, soloist and orchestra area. It will require further investigation because I did not entered such information at the beginning so it may not be a migration issue.
Great tool though keep on. 
|
|
 IP Logged |
|
|
|
Andrei
Administrator
Email
Posts: 1172
|
 |
Re: Migration FAQ
Reply #1 on: Jul 19th, 2006, 10:33am |
Quote | Modify
|
on Jun 21st, 2006, 1:20pm, miclev wrote:I think that some information is missing in the FAQ regarding Version 6 migration process. Some of the following should be present.
When is the version 6 GA is expected? I think I saw a comment in one of the FAQ that version 6 would keep the Beta suffix. I’m I right or is it a wrong interpretation? |
No, it won't keep beta suffix. All I can say that it will be released this summer
Quote:| Could a version 5 database be opened directly using version 6 without loss of information or should an Export – Import process be used instead? |
Yes, v5 and v6 databases are fully compatible.
Quote:| Should version 5 be removed before installing version 6 or can it be installed over? Is the registration code preserved if installing over or must it be entered again? |
You don't have to remove v5, but it is recommended if you have build older than 5.2 because older builds can cause errors during v6 installation (specifically, error 5). To get rid of these errors, you'd need to restart computer or manually remove v5.
Quote:| Could version 5 registration code be used with version 6 or must a new one be requested. |
V6 requires a different key. However, if you have your old v5 key, you can enter it using "Enter registration" application in start menu (NOT in the OrangeCD Catalog application). Next time OrangeCD Catalog starts, it will connect to server and pull a new key for you at no charge.
Quote:| Will there be an « upgrade » fee for current users or will it be free when GA of version 6 be out? |
Current customers will never be charged upgrade fees per their user agreements. There are no plans to change policy for our future customers either.
Quote:| My first impressions of version 6 are pretty good in regard of classical information. During my tests I did opened my database and it did not complain but I think that some data « disappeared » in the conductor, soloist and orchestra area. It will require further investigation because I did not entered such information at the beginning so it may not be a migration issue. |
Look for conductor/soloist information in Credits tab of album properties. It's moved there.
|
|
IP Logged |
|
|
|
|
