Reported By: Michael Urban Reported On: 9/25/1998 For: Version 1.05 Build 1
# 230No Default Printer Defined in Windows Causes an Access Violation in Database System Utility I can't start up the DBSYS utility after switching to a new PC, it gives me an access violation at startup.
CommentsThis problem was reported by several developers and we were stumped until Michael pointed out that he solved the problem by switching his default printer to his DeskJet from a faulty Microsoft Fax printer driver. It seems that the DBSYS and DBCUST utilities had printing initialization code in them that was sensitive to there not being a default printer. This problem has been fixed so that the AV at startup is gone and an appropriate error message is displayed if you try to print without a default printer (or any printers) installed.
ResolutionFixed Problem on 10/24/1998 in version 1.07 build 1