Tom,
"If I move the compiled app to any of the networked computers, and run
directly from them it works fine."
Whatever it is, it is related to the machine according to what you say.
It will be extremely difficult for others to help you when your issue is
related to the environment in which it is being run.
So far, no one has come forward with the same issue or history of the same
issue, for you to be able to bank on their experience.
Can you create another report from scratch and begin adding elements to the
code used to call the report until you get to the point that it breaks?
This is the brute force method I employ when there is nothing to go on.
Tedious work no doubt, but often the answer is found.
----- Original Message -----
From: "TOM HART" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Sunday, September 12, 2010 5:57 PM
Subject: [RBASE-L] - Re: 9.0 compiled printer problem
I do use the UNC. If I move the compiled app to any of the networked
computers,
and run directly from them it works fine. With 7.6 I have never had a single
problem. There is no code in the reports, it just does not seem to like the
where clause. This has only started when compiled with 9.0. I do have the
most
current updates. I have even tested the printer by using the property
command
to print screen(which has been my temporary work around).
Tom Hart
________________________________
From: A. Razzak Memon <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Sun, September 12, 2010 4:35:04 PM
Subject: [RBASE-L] - Re: 9.0 compiled printer problem
At 05:07 PM 9/12/2010, TOM HART wrote:
I just cannot seem to understand why it will run on the
computer hosting the program but will lock up on all
other network computers.
Without knowing all details (which is always a challenge
when the crystal ball doesn't work), I suggest the following:
1. Find the exact difference between the computer hosting
the program vs. other network computers.
2. Make sure that the network computers are mapped with
the same exact drive letters as on the computer hosting
the program. This may be a problem which you need to
address when a hard-coded drive letter is used.
Use UNC mapping method to avoid all these issues.
In a network environment, the Universal Naming Convention
(UNC) is a way to identify a shared file in a computer
without having to specify (or know) the storage device it
is on. In Windows operating systems, Novell NetWare, and
possibly other operating systems, the UNC can be used
instead of the local naming system (such as the DOS naming
system in Windows).
In Windows operating systems, the UNC name format is:
\\servername\sharename\path\filename
3. Check and verify the installed/shared printers and
assigned printer names. This may be a problem which
you need to address when a hard coded printer name is
used for PRNSETUP command and the appropriate printer
drivers are not properly/successfully installed.
4. Check and verify the user access/rights on the computer
hosting the program vs. other network computers.
The above simple checklist alone should provide you with
some blue's clues ...
Very Best R:egards,
Razzak.
