Support for Buggy V8?

[Darren B]

Remmo

Thank you for your comments, i contribute little compared to some but i new nothing 3 years ago (and still no little - before someone gets it in)

Good Luck

Darren

[los_design]

Remmo

Thank you for your comments, i contribute little compared to some but i new nothing 3 years ago (and still no little - before someone gets it in)

Good Luck

Darren

Beat me to it

[Darren B]

I knew either you Lee Jont or George and possibly Tracy would

[TraceyHand]

I knew either you Lee Jont or George and possibly Tracy would

I most certainly would not

*wonders what you all must think of me...decides I probably don't want to know*

[los_design]

I knew either you Lee Jont or George and possibly Tracy would

Glad I did not disappoint

Off for a pot of coffee now, gonna be a long night....why does every bloody site you upgrade overwrite the poxy protx script and you need to re-upload a big site

Hey ho..

(ps this is now a v8 bug.....honest)

[Darren B]

I do not even change the settings in the order recommended as it always overwrites the bloody secret key

[los_design]

I do not even change the settings in the order recommended as it always overwrites the bloody secret key

Maybe one for the wishlist?

Race you....1,2,3 GO

[Jan]

Such as trying to link Quickbooks to Actinic using the Quickbooks Link application, translation tables and manually typed unique product references in Actinic.

I don't think that there were any significant changes to the way Actinic links to Quickbooks in V8.

Regards,

[PeterThake]

Hi Jan, (or may I call you Jo? )

I did not have Quickbooks Link when I had v7 Catalogue, and it was a big factor in my decision to invest in v8 business. If there were no changes between link 7 and link 8 then these problems must have been present all the time . I get the impression that Link is not something that is widely used, especially with QB?

The bug with products where a description field length of 20 over-flows the field length limits when they are duplicated (when actinic adds the 1! type code to the front of the descriptor) was a new bug according to Actinic. Once the field overflows both Actinic and the Link application get really unhappy.

Another other bug/feature of Link is that the translation table fields are case sensitive when matching records. This was known by Actinic, but sadly is not documented anywhere.

Finally there is another (new?) Link bug/limitation: the field length of the QB product name in the Link translation table is limited to 50 characters although there is no such limit in QB. This puts a real limitation on the use of nested products in QB. eg.

eg "Yomega Assemblies:Power Brain XP:Power Brain XP Blue" = 52 chars long = does not translate nor do any subsequent records.

All of these can be worked around once you know about them, but as a newbie to Link they were all a pain in the rear and cost me many frustrating hours tinkering around and shop down time.

I hope that by posting here others might avoid these pitfalls.

[TraceyHand]

Hi Jan, (or may I call you Jo? )

only if you don't like all your bits where they are

[Jan]

I hope that by posting here others might avoid these pitfalls.

Thanks, so many people don't do this which is a shame as it is a real help for others in the future. The duplicates bug is a new one, I'm not sure about the link issues, but I suspect they are in V7 as well.

The link programs do require quite a bit of setting up but are a real timesaver once they are in place.

Regards,