bb.donnay-software.com

Roger,

For many years our users have printed their logo on their forms and invoices. Due to path changing on their work station, we have had to stipulate location in an ini file, such as w:\oiswin\mylogo.bmp.
We have one very large user that has users printing one form all day, maybe 50 users printing off an on, and the logo is not printing. Ends up some (not sure how many) have a different drive letter, so that would be an obvious issue, which we told him. Not sure if the have the long path available or not.
Question: if 2-3 users attempt to print at the same time, will it just not print the logo for 2, or all of them, or is the server supposed to handle that. There is no locking or anything, we just use the standard bitmap name and your routine.

@ c1,c2,c3,c4 DCPRINT BITMAP bitmapfl ;
PRINTER oPrinter autoscale

Just want to have an educated answer if he says it still does not work.

Fred
Omni

hi,

i´m not Roger but i try to answer your question

omni wrote:For many years our users have printed their logo on their forms and invoices. Due to path changing on their work station, we have had to stipulate location in an ini file, such as w:\oiswin\mylogo.bmp.
We have one very large user that has users printing one form all day, maybe 50 users printing off an on, and the logo is not printing. Ends up some (not sure how many) have a different drive letter, so that would be an obvious issue, which we told him. Not sure if the have the long path available or not.

still using "old" Lanmanager Syntax with Drive Letter ? why not use UNC Path ?

when oBitmap:loadfile("\\Server\Path\mylogo.BMP") you get .T. / .F. for Success ... check it.

omni wrote:Question: if 2-3 users attempt to print at the same time, will it just not print the logo for 2, or all of them, or is the server supposed to handle that. There is no locking or anything, we just use the standard bitmap name and your routine.

@ c1,c2,c3,c4 DCPRINT BITMAP bitmapfl ;
PRINTER oPrinter autoscale

Just want to have an educated answer if he says it still does not work.

IMHO all Files on Server must be lock if workstation want to access it, but there are difference how Server can lock.

DLL are design for share so you can make a single Resource.DLL for your Logo.
if you do not like "hardcode" you can store BMP in a MEMO ( Type "V" ) and load it in your Application

Fred -

I'm pretty sure that your problem is a wrong path.

Put some debugging in the code like so:

wtf bitmapfl, Fexists(bitmpafl)

Roger

Fred,

Why not simply copy the desired graphic image(s) into the same directory which your data exists, that way you will be certain of its' location and it will be accessable to every user/location.

Thanks everybody.

Ends up the users hard drive was a different letter. The users do not have access to the \\server... path in their set up (not under our control for that issue). Other programs keep changing their default path, so we keep changing it back in our app. A real pain, and the other programs are changing it to the c-drive, which is why we hard code a drive letter in the ini file for the logo. At any rate, not a problem after the drive letter was reassigned.
Still old-school, so trying to come up with a better way that all users can use. rarely an issue. Obviously, the long path is the way to go, since the server path never changes.


thanks

Fred
Omni