Sage 100

Sage 300 (Accpac) version 5.6 - it seems like every time I create a custom Crystal report that uses a view or stored procedure, the report runs fine from within Crystal, but when run from within Sage 300 I get a ""logon failure"" error. Sage support answer was to use ""trusted connection"" in the Crystal connection setup, but that means you have to add windows users into the SQL Security setup. Anyone have a better idea?

How many Sage 300 partners are in this group besides Phil and myself? Maybe we could have a Sage 300 group???

Excellent idea.

@ThereseLogeais and @PhilMcIntosh - Would you two be willing to head up this group, develop some marketing ideas for OASIS and perhaps do a webinar focused toward Sage 300 Users? @PeterWolf could be your admin team contact.

@JeffSchwenk - do you mean ideas for marketing OASIS to 300 consultants? Do any of he 90minds members from DSD actually work with 300? (In other words, would @ThereseLogeais and I be Chiefs without any Indians?)

That's what I was thinking Phil. Looks like a pretty small group....

Actual solution to the specific problem: I created a VB.Net program as a wrapper for the report, and put that program on the Sage 300 desktop. You do need to install the Crystal runtime for dotNet (use 32bit, the 64bit version can be flaky) on each workstation where the program/report will be run.