Unable to find the relevant thread...

[george]

...is it possible and/or sensible to c&p a catalog database into v8 from an earlier version? Unless the original v8 database is different, with more variables as default etc?

This would transfer the data, but keeping the actual v8 conversion as clean as possible?

What other info needs to be transferred over? Other than theme tweaks of course.

Cheers 'm Dears.

[leehack]

I have read recently in the V6 forum and in here that in order to upgrade an old say v3 or v4 catalog, you paste the database into the new software and it will automatically upgrade etc.

As the new fields in v8 will not appear in older versions, i would imagine these will just stay empty and not affect anything. To upgrade V3 or V4 i think you are advised to move up to v7 and then upgrade to v8. This tells me that the database upgrading must work at some level, how good is anyones guess and probably different in each case. I would imagine that actinic has stepped up its versions of access over the years which makes this possible.

In answer to your question, i think manually upgrading to V7 and then auto upgrading to V8 is the best way.

[george]

Moving from v7 Lee.

Was having a look at the different default databases (both Access 2000) and the v7 and v8 are totally different. I'm thinking that c&ping a v7 into v8 would simply overwrite some v8 choices/options that v8 now has?

I know I could just bang on and try it, but I like to have some idea of the potential outcome...


...if I am to upgrade to v8, I'd need to do it with a minimum of fuss to our business, even if that meant sitting with a pretty standard theme for a few days/weeks/months/YEARS!?!?

[leehack]

Install V8 as its own entity George and try your upgrade on there whilst your v7 site sites there doing its normal thing. They can operate totally independant of each other. If you wanted to be really cautious, install v7 on a second PC, import a current snapshot and then try to upgrade it on that pc, leaving the v7 well alone.

If your site is heavily modified, i would predict a 90% chance of problems, some of which will make trying to correct them a hell of a lot longer than just applying a new theme and starting again. General consensus seems to be if standard, then upgrade, if heavily amended, start afresh as you will end up bald.

[george]

Hmmm. v8 appears to have much of the regular (v7 etc) ActinicCatalog.mdb under ActinicCatalog.ldb, which is a locked Access file.

[RuralWeb]

Bung it in - Ive done it a couple of times now and it worked ok.

[george]

Went for it, and it seized v8. First showed a number of errors, too many to list (inc Warning ones) , then wouldn't let me close Catalog. Had to reboot pc. Then c&p'd the mdb from the Original folder. All is well again, but back to square one.

I'll experiment a bit more, as it'd be nice to have a `clean` site as ours has been upgraded every time since v6.

[cdicken]

Hi George (and anyone else reading this).

Please remember that this does work, but it won't convert any custom properties into new 'user-definable variables', so any data in these fields will be lost.

[jont]

t'd be nice to have a `clean` site as ours has been upgraded every time since v6.

George - when you import the v7 there are several options about upgrading the site - selecting "apply default theme" .. or similar words will be the best starting point IMHO having seen your ACD (oo-err)

[RuralWeb]

Ive found that "flushing" the site through V7 to get rid of any customisation before upgrading can help then upgrade. You could then export the upgraded V8 site into a new V8 site.

[george]

Ive found that "flushing" the site through V7 to get rid of any customisation before upgrading can help then upgrade. You could then export the upgraded V8 site into a new V8 site.

Does that translate into changing the current theme to a blank(ish) one in v7, then saving a snapshot which is then upgraded into a current theme in v8? Resulting with a v8 site with no (or at least minimal) tweaks?

Christ, you dudes must think I'm Fred Flinstone lol.

[RuralWeb]

Does that translate into changing the current theme to a blank(ish) one in v7

Yep - use one of the clean themes - I dont use the css one though.

Love Barny

[george]

George - when you import the v7 there are several options about upgrading the site - selecting "apply default theme" .. or similar words will be the best starting point IMHO having seen your ACD (oo-err)

Aye, thats option A. Just thinking about your advice on keeping the v8 base site as clean as possible though. ie very little traces of v7. It'll be problematic enough for yours truely to adjust to v8 anyway, without bits of (v7) html (or whatever) shrapnel flying everywhere.

[george]

So. After working on your old/new theme on the spare pc, whats the best routine for updating it a couple of weeks/months down the line with your latest v7 orders/new stock/latest stock levels etc etc into your new v8 modded site?

(I think I know the answer, but I'd rather confirm)

How am I finding v8? Erm, not easy when you're only getting a little time on it here and there. I do have time perhaps later on at night but thats when my concentration is not at its best I'm afraid. I've just realised that I don't really adjust the design much apart from changing some offers or adding some links etc, so once its set up its just a case of carrying on as normal... I think. Reading this forum does make you aware of potential problems of course, which helps. Regarding a new look, there ain't much in the standard templates to choose from really, which is dissapointing. Unless I need to give myself some un-needed stress by looking at using one of the clean layouts. As always, just saying it like it is folks.

[george]

*coughs when walking, falls over printer on floor, crashes onto keyboard and accidentally brings thread back to the viewing area, apologises*