Just installed clean version of 7.0

hwnd=Get_Property(@Window, 'HANDLE')

stat=Print_Init(0,"Student Record", hwnd)

status=set_Printer('Put ink on the paper')

status=print_End()

Prints a blank page.

hwnd=Get_Property(@Window, 'HANDLE')

stat=Print_Init(0,"Student Record", hwnd)

status=print_Text('Put ink on the paper.')

status=print_End()

This works. Why won't set_Printer work?

Your sentence…

status=set_Printer('Put ink on the paper')

is in error. Try this sentence…

status=set_Printer('TEXT','Put ink on the paper')

It should work.

Okay, so I typed it wrong. Actually it is correct in my program,

i.e. status=set_Printer('TEXT','Put ink on the paper')

I think I found the problem in that there appears to be two printing processes within OI. It all depends on how you start and stop the printing process:

hwnd=Get_Property(@Window, 'HANDLE')

stat=Print_Init(0,"Student Record", hwnd)

   various print statements like stat=print_Text('Put ink...')

status=print_end()

or

status=set_Printer('INIT','Student Record')

   various statements like stat=set_Printer('TEXT','Put...')

status=set_Printer('TERM')

Appears to me the last example is OIPI which seems to have infinite capability but, but, but I am not printing watermarks etc. Just simple text. Except I want bold and underline capability. Does anybody know how to set the font using the simple printing process?

Larry,

It looks like you figured out that you were mixing two different print libraries incorrectly.

We never used the Printer DLL functions because they never completely worked as advertised. I highly recommend you re-consider using the OIPI event for simple stuff. I believe the syntax is just as easy and you will only have to deal with learning and using one form of printing within OI.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

You may be correct but this OLD Arev programmer finds OIPI way too complicated for what I am doing. All I need now is a help file on how to use the system. I have figured out Utility to get my fonts etc but there must be an font $insert someplace where all that has been done. Have not found it yet.

Printing and "Cell Hell" have delayed my using OI till now. I purchased Ver's 1,2,3 over a hundred years ago and have been a Works member for several years. Have never used OI because my customers have a lot of tables and OI's implementation of MV data is bad at best. Like, where is the cursor now? They simply refuse to give up Arev functionality.

What makes me mad is that you pull up a dictionary record and it is BEAUTIFUL. Why, why….. can that not be implemented in the whole system? I now know that it can be done. Problem is that I am 70+ years old and I worry that I may never see it fixed.

I continue to come back to OI with each new release and do a little more work. My printing worries are over. I think I see light at the end of the tunnel. But is that the Lord coming to get me?

I use the "simple print" functions too. For fonts you might want to try…

SUCCESS=PRINT_SETFONT(FONT)

It works for me.

Larry,

Richard provided you with a command that will hopefully work for you. If you post your code using the Printer DLL routines I'll post the equivelent code using the OIPI to give you an idea of how it would translate.

Believe me brother, I certainly know what you are going through. Printing has/had always been the #1 reason why I never converted to OI until Tony Splaver released the OIPI. Fortunately this happened relatively early in OI's history (we began using it when 3.0 hit the scene) so we have been used to it for about 10 years now.

What makes me mad is that you pull up a dictionary record and it is BEAUTIFUL. Why, why….. can that not be implemented in the whole system?

I'm not sure what you are referring to here. Are you talking about the way the Table Builder prints dictionaries?

dbakke@srpcs.com

SRP Computer Solutions, Inc.

What I am refering to re the dictionary is in Table Builder. The cell you click on turns yellow. Beautiful! You immediately know where you are. Oh to have that functionally in my edit tables without having to write and maintain my own code, like that described in "Cell Hell".

Thank you very much re the offer to help me with OIPI coding. Actually I got my program to work when I figured out there are two printing processes in OI.

My grandson has converted our Ski Reservation System printing to OIPI so I know the code required. He is just finishing his associate degree and I planned to have him convert one of my big (20 user) systems to OIPI before he goes on to graduate school. No need now. I have converted several reports so I feel like I'm on a roll. Only 51 more to go.

So what to do with my grandson? He gets to work on our car dealership system that demands OIPI for several forms.

Glad to hear I am not alone in this. Converting from Arev printing is really not that bad once you get all the fonts figured out. I've been running Utility to get them and can now just use my $insert. This way I can use my Arev code with no changes insofar as the statements related to font changes, like ul.on, ul.off etc.

Thanks for the encouragement.

Larry,

I see what you mean about the Table Builder. Well, they had to do the same amount of programming you would if that makes you feel better!

I hate to be a commercial, but if OI's edittable is truly a problem for you then you might want to consider an alternative. We have an OLE edittable that was designed to remedy much of what you are concerned about. If you are going to NOLA then you could see it first hand. Otherwise, we should have an evaluation download on our website within a few weeks.

If you are doing an AREV-]OI conversion, have you considered using Tony Splaver's Direct Print utility? It can save you a lot of time converting your reports.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

View this thread on the forum...