Technical and Installation Discussions

[BigLouie]

Every time I have a printing problem in MAS I am able to track it back to non-existent printers in the Printer/Fax folder.

[RoadRacer]

You may be onto something, Big Louie. We have Terminal Services printer sessions that don't close. Right now, I see several instances of multiple sessions of a particular network printer from the same workstation. In the past, we have occassionally manually deleted these sessions in TS. Perhaps if we figure out how to prevent these from occurring, we will eliminate the Crystal problem, too.

Thanks.

[glrickert]

For whatever its worth, we are heavy users of the WO module (MAS 90 version 4.4) and we do experience problems

with WO Traveler printing about once ever 3-4 months or so.  Our reseller has to be called in and paid a fee to fix.  I've been

told the problem is caused by crystal dlls getting corrupted because of the old file structure in WO for UDF's.

In general, I agree with RoadRacer's comments that WO is just not a robust module.  The reports are ancient, the screens are

not user friendly, the whole module is just buggy.  We have open cases with Sage on how false requirements for WO can be

created, how components are routinely missing from Material shortage reports, etc.. Why hasn't Sage updated WO to the business

framework?   Wonder what the established base of WO users are out there?

[DFeller]

It's not the Crystal DLLs getting corrupted; it's the Crystal work tables.  Clearing them out is a fairly easy process -- you should be able to do this yourself and not involve your reseller.

Dawn

[glrickert]

Thanks DFeller, can you tell me how to do that?