network printer problems

fweeee

A client of ours, using Navision 3.70, is having some problems with networked printers on a server. They have application server installed on this machine, which periodically will print out various reports to various networked printers (which are in remote locations - they use terminal services or something to connect them).

The problem is, when they reboot the server, the printers no longer work. They have to reselect the printers within navsision before it will work again.

Now I have heard of this problem before - I think we called it the "NE problem" before, as it was something to do with the ne number given to the printer by the OS. This changes when rebooted, which confuses Navision.

Has anyone else ran into this problem? And if so, how did you go about fixing it?

Thanks.

Shanon.

kine

1) This was chenged in 3.70B client. It is not including the NE in the name of the printer now...

2) You can modify the function FindPrinter in CU 1 - you can change it to ignore the NE part of the printer name

Timo_Lässer

FindPrinter(ReportID : Integer) : Text[250]
CLEAR(PrinterSelection);

IF NOT PrinterSelection.GET(USERID,ReportID) THEN
  IF NOT PrinterSelection.GET('',ReportID) THEN
    IF NOT PrinterSelection.GET(USERID,0) THEN
      IF PrinterSelection.GET('',0) THEN;

// > TL4.00:02 >>>
IF PrinterSelection."Printer Name" <> '' THEN
  IF NOT Printer.GET(PrinterSelection."Printer Name") THEN BEGIN
    Printer.RESET;
    Printer.SETRANGE(Name,SELECTSTR(1,PrinterSelection."Printer Name"));
    IF Printer.FIND('-') THEN
      IF Printer.COUNT = 1 THEN  // only if unique result
        PrinterSelection."Printer Name" := Printer.ID;
  END;
// < TL4.00:02 <<<

EXIT(PrinterSelection."Printer Name");

Savatage

let's just link these...

http://www.mibuso.com/dlinfo.asp?FileID=25

fweeee

Thank you - I will look into these solutions.

I should have been more specific - Although they are using a 3.70 executables, it is a 3.01B database. (The client has been upgraded by the C/Side code has not).