Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Printing On Dot Matrix Printer From VFP
Message
De
18/07/2001 16:58:53
 
 
À
16/07/2001 23:35:16
Devrishi Bhogra
Escorts Claas Limited
Faridabad, Inde
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00529557
Message ID:
00532214
Vues:
12
>hi john!!

>thanx buddy for ur help. John but my problem is different.
>Let me explain...

>I recently shifted from Foxpro 2.6(dos) to vfp 6.0. But i found printing on a >dot matrix printer is really tough in windows enviromnet.

>John the solution which u have given me will work for the processed report >file.
>But in case i am printing directly on printer then what to do ?

>Also please put some light on ldmp variable (var to tell if the dm printer is >local). is it a system defined variable because u haven't declared it in ur >code sample.


>My current problem is...when i send Escape Codes[chr(27)+(chr(120)+"0" for >draft quality] to printer although Printing mode changes but it ejects a page >first.which is really hurting..

>Please help john...and tell me ur approach of handling dot matrix printer.

>Regards

>Sunny

hi Sunny

i have an app that is used in the service call industry. some offices have a single dm printer, some have more, so when the app is run for the first time on a workstation, the app checks for a certain .mem file. if the .mem file is not there, the app asks if there is a local dm printer and creates a .mem file to store the answer to that question. if there is a local dm printer, the app sends output to that printer, else it sends output to a dm printer attached to one of the other workstations. the path for this printer is stored under the app setup where they store things like company name etc. if the .mem file is found when the app is loaded, it restores a logical var telling this instance of the app that the dm printer is either .t. (local) or .f. (not local). that var is ldmp.

the only way to get rid of the blank page eject is to first print your report to a file (which keeps all the control codes intact), and then use the copyfile API to print that file to the dm printer. every time you print the report to that file, that file will be overwritten unless you specify that the info must be printed to the file 'additive', then you will have your previously run report info as well as what you have just run.

if is am not understanding your problem correctly, please let me know.

best - john
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform