NOW LIVE! Today's the day you meet your new best friend. You don’t have to leave Wolfy behind... In 'Pets & Sidekicks' your companions level up with you!

Reply to thread

Message: <blockquote data-quote="Vpenman" data-source="post: 467527" data-attributes="member: 6794">Well, I started out pretty much opposed to both XML and Access, but Hollywood's well-reasoned arguments have almost won be completely over.Basically, I have to agree with Hollywood's assessment that the problem is not primarily with the technology chosen but rather with how it was implemented.XML is fine as long as it is in addition to the regular Windows print options and the browser upgrades needed to use it are included on the product CD with an almost, automatic install (don't mean to be putting words in anyone's mouth here).The main problem with Access, as used in E-Tools, is that you can't really create and share custom data unless you have and know how to use Access.  A secondary problem is that many people need to download the correct ODBC in order to be able to use the database at all.If a front and back end were in place to allow normal users to create and share custom data and the ODBC had been provided on the E-Tools CD, you are pretty much down to the following trade off -- the benefits of allowing people to directly use Access to create custom data without restriction vs the problems such creation could create either accidentally or on purpose.As the person at Evermore who answers all of the e-mails we receive on the Core Rules products, I am probably more in touch with people who aren't necessarily top notch computer users than is generally the case.However, other than that last point, I believe I am now in Hollywood's camp.Finally, FDWojo, thank you for the kind words on the Core Rules products.Victor</blockquote>

Verification