Hello all, This is my first post to your community. I am trying to find someone that will convert a single (dynamic) report from DOS/Clipper/Symscript/Dbase to a windows print processor that can retain the exact look and feel of the original. We have exhaused ourselves looking for a reporting tool that can do this, and have not found one. We have found that the report must be hand coded as the original.
Summary: Help sys/Clipper & Summer '87 compiler app. Download: ahelp5.zip (Nov 28 1990, 192.1K). Summary: Link any data file with Clipper programs.
The rport grows in two dimentions Across and Down, but they take up the same areas on each page. For example the top portion about 4-5 inches is comprised of columns that end up on the same page position on all pages depending on the number of columns. The bottom section grows down in similar fashion to the way the upper section grows across. It is currently coded in Summer 87 with Symscript to generate the PCL for exact placement. I need to move this to windows with an Access or SQLServer database but really want to retain the original look and feel. Please contact me if you think you are capable of doing this conversion for me.
I do not think it will take too long. The rest of the program is currently coded in Access and should be completed in the next month. Thanks for you time, Tim Re: Clipper Summer 87 report conversion on Fri, 17 Nov 2000 17:05:58 +0100. I think you have a problem.
You need to keep the program in xBase. I'd say you have wasted alot of your time converting to a language that you have little control of.
I simply will not do any Access coding beacuase of these kinds of problems. The best you can do is to convert the Clipper procedures that print the report to Xbase. I'd look at Topdown or Express addons to help since converting to GUI is not an easy thing. Jim 'Raguel' wrote in message -software.com. Hello all, This is my first post to your community. I am trying to find someone that will convert a single (dynamic) report from DOS/Clipper/Symscript/Dbase to a windows print processor that can retain the exact look and feel of the original.
We have exhaused ourselves looking for a reporting tool that can do this, and have not found one. We have found that the report must be hand coded as the original. The rport grows in two dimentions Across and Down, but they take up the same areas on each page.
For example the top portion about 4-5 inches is comprised of columns that end up on the same page position on all pages depending on the number of columns. The bottom section grows down in similar fashion to the way the upper section grows across. It is currently coded in Summer 87 with Symscript to generate the PCL for exact placement. I need to move this to windows with an Access or SQLServer database but really want to retain the original look and feel.
Please contact me if you think you are capable of doing this conversion for me. I do not think it will take too long. The rest of the program is currently coded in Access and should be completed in the next month. Thanks for you timeTim Re: Clipper Summer 87 report conversion on Sat, 18 Nov 2000 18:04:22 -0500. OK, Many mistakes have been made, and much time has been wasted.
Much of which might have been posting here. (Think he hit a hot button and got me riled up!) But. I am looking to PAY someone to do a conversion of the report only! Does anyone want to make $$ doing this? It seems simple enough to understand, I cannot do it, or I would have done it. So now I want to pay to have it done.
I would like to have a windows executable that I can call from my Access program, pass the policy number or string or multiple policy numbers to the EXE that handles the print routine and either Preview on screen or Print to paper. Thanks, and I hope I am a bit more clear this time on what I am wanting to have done.
BTW, was this the Job Posting Board of Xbase, or the ignore the question and flame board? 'James Loughner' wrote in message -software.com. I think you have a problem. You need to keep the program in xBase. I'd say you have wasted alot of your time converting to a language that you have little control of.
I simply will not do any Access coding beacuase of these kinds of problems. The best you can do is to convert the Clipper procedures that print the report to Xbase.
I'd look at Topdown or Express addons to help since converting to GUI is not an easy thing. Jim 'Raguel' wrote in message -software.com. Hello all, This is my first post to your community. I am trying to find someone that will convert a single (dynamic) report from DOS/Clipper/Symscript/Dbase to a windows print processor that can retain the exact look and feel of the original. We have exhaused ourselves looking for a reporting tool that can do this, and have not found one. We have found that the report must be hand coded as the original.
The rport grows in two dimentions Across and Down, but they take up the same areas on each page. For example the top portion about 4-5 inches is comprised of columns that end up on the same page position on all pages depending on the number of columns. The bottom section grows down in similar fashion to the way the upper section grows across. It is currently coded in Summer 87 with Symscript to generate the PCL for exact placement. I need to move this to windows with an Access or SQLServer database but really want to retain the original look and feel. Please contact me if you think you are capable of doing this conversion for me. I do not think it will take too long.
![Clipper Summer 87 Software Downloads Clipper Summer 87 Software Downloads](http://www.codemag.com/Article/Image/1409061/image2.png)
The rest of the program is currently coded in Access and should be completed in the next month. Thanks for you timeTim Re: Clipper Summer 87 report conversion on Fri, 17 Nov 2000 20:03:38 -0500. Sorry I didn't notice what board it was posted on Send me the report code I'll take a look. But how exact is exact?? I can place the text but GUI printing tends to be a bit variable. Do you have a Fixed font you want to use?
If you want a new print out to be indestingushable from an old I'm not sure it can be done. Jim Loughner 'Raguel' wrote in message -software.com. OK, Many mistakes have been made, and much time has been wasted. Much of which might have been posting here. (Think he hit a hot button and got me riled up!) But.
I am looking to PAY someone to do a conversion of the report only! Does anyone want to make $$ doing this? It seems simple enough to understand, I cannot do it, or I would have done it. So now I want to pay to have it done. I would like to have a windows executable that I can call from my Access program, pass the policy number or string or multiple policy numbers to the EXE that handles the print routine and either Preview on screen or Print to paper.
Any takers? Thanks, and I hope I am a bit more clear this time on what I am wanting to have done. BTW, was this the Job Posting Board of Xbase, or the ignore the question and flame board? 'James Loughner' wrote in message -software.com. I think you have a problem. You need to keep the program in xBase.
I'd say you have wasted alot of your time converting to a language that you have little control of. I simply will not do any Access coding beacuase of these kinds of problems. The best you can do is to convert the Clipper procedures that print the report to Xbase. I'd look at Topdown or Express addons to help since converting to GUI is not an easy thing. Jim 'Raguel' wrote in message -software.com.
Hello all, This is my first post to your community. I am trying to find someone that will convert a single (dynamic) report from DOS/Clipper/Symscript/Dbase to a windows print processor that can retain the exact look and feel of the original.
We have exhaused ourselves looking for a reporting tool that can do this, and have not found one. We have found that the report must be hand coded as the original. The rport grows in two dimentions Across and Down, but they take up the same areas on each page. For example the top portion about 4-5 inches is comprised of columns that end up on the same page position on all pages depending on the number of columns. The bottom section grows down in similar fashion to the way the upper section grows across.
It is currently coded in Summer 87 with Symscript to generate the PCL for exact placement. I need to move this to windows with an Access or SQLServer database but really want to retain the original look and feel.
Please contact me if you think you are capable of doing this conversion for me. I do not think it will take too long. The rest of the program is currently coded in Access and should be completed in the next month. Thanks for you timeTim Re: Clipper Summer 87 report conversion on Sat, 18 Nov 2000 22:19:55 -0500. How about 99%? I will gather and send you end results and the PRG in the next day or two.
Tim 'James Loughner' wrote in message -software.com. Sorry I didn't notice what board it was posted on Send me the report code I'll take a look. But how exact is exact?? I can place the text but GUI printing tends to be a bit variable. Do you have a Fixed font you want to use?
If you want a new print out to be indestingushable from an old I'm not sure it can be done. Jim Loughner 'Raguel' wrote in message -software.com.
OK, Many mistakes have been made, and much time has been wasted. Much of which might have been posting here. (Think he hit a hot button and got me riled up!) But. I am looking to PAY someone to do a conversion of the report only! Does anyone want to make $$ doing this? It seems simple enough to understand, I cannot do it, or I would have done it.
So now I want to pay to have it done. I would like to have a windows executable that I can call from my Access program, pass the policy number or string or multiple policy numbers to the EXE that handles the print routine and either Preview on screen or Print to paper. Any takers? Thanks, and I hope I am a bit more clear this time on what I am wanting to have done. BTW, was this the Job Posting Board of Xbase, or the ignore the question and flame board? 'James Loughner' wrote in message -software.com.
I think you have a problem. You need to keep the program in xBase.
I'd say you have wasted alot of your time converting to a language that you have little control of. I simply will not do any Access coding beacuase of these kinds of problems. The best you can do is to convert the Clipper procedures that print the report to Xbase. I'd look at Topdown or Express addons to help since converting to GUI is not an easy thing. Jim 'Raguel' wrote in message -software.com. Hello all, This is my first post to your community. I am trying to find someone that will convert a single (dynamic) report from DOS/Clipper/Symscript/Dbase to a windows print processor that can retain the exact look and feel of the original.
We have exhaused ourselves looking for a reporting tool that can do this, and have not found one. We have found that the report must be hand coded as the original. The rport grows in two dimentions Across and Down, but they take up the same areas on each page. For example the top portion about 4-5 inches is comprised of columns that end up on the same page position on all pages depending on the number of columns.
The bottom section grows down in similar fashion to the way the upper section grows across. It is currently coded in Summer 87 with Symscript to generate the PCL for exact placement.
I need to move this to windows with an Access or SQLServer database but really want to retain the original look and feel. Please contact me if you think you are capable of doing this conversion for me. I do not think it will take too long. The rest of the program is currently coded in Access and should be completed in the next month. Thanks for you timeTim Re: Clipper Summer 87 report conversion on Mon, 20 Nov 2000 10:02:25 -0600.
A tale about the origin of Clipper There is a tale about the origin of CA-Clipper. Whether it is true or not, few people know, but “insiders” have said that it is not far from the truth. One day in a seafood restaurant in Malibu, California, an Ashton-Tate employee and a consultant friend were having lunch. They were expressing their annoyance at the fact that Ashton-Tate had not created a compiler for the dBase language.
The two thought that maybe they should have a go at starting up a new company to create the compiler. As the excitement grew and the ideas flew, the issue of a product name came up. One of the two noticed a picture of a sailing ship on the napkin (after all this was a seafood restaurant). It was a clipper ship — a sleek, speedy, and elegant thing.
That seemed to describe what they were trying to create. What about the company name?
![Clipper summer 87 software downloads download Clipper summer 87 software downloads download](http://www.dstorm.eu/pictures/decals/ced72213_1.jpg)
The menu answered that question — the restaurant name was Nantucket Lighthouse. And so Nantucket’s Clipper was born. The consultant was Barry ReBell and the Ashton-Tate employee was Brian Russell. Since that time there were four “seasonally” named versions of the compiler: Winter 85, Spring 86, Autumn 86, Summer 87. Very “California” These early versions clearly billed themselves as dBase compilers, with the Summer 87 version displaying “dBase III® compiler” on the floppy disks and documentation. Many programmers using Clipper at the time were really “just” dBase programmers with a tool to create faster programs. So it was quite a shock to them when Clipper 5 was released.
“What have they done to our language?”, they asked. Local variables? But there were also those of us who had strained against the limitations of the dBase language — the lack of modularity, the clumsiness, the vulnerability of public and private variables.
So we recognized that Clipper 5 was a turning point in the history of the Xbase language. No longer billed as a dBase compiler, Clipper became an “Application Development System”. A real language. Well, maybe not as real as C, but getting there. In fact, many Clipper 5 concepts were borrowed from C and other languages.
The increment operator ( ) and expression lists, for example, seem to have come from C, while code blocks may have been inspired by SmallTalk This article borrowed by courtesy of author, from. Please look at for continuation of this post. As a computer software term, the word “Clipper” has two meaning: 1- A 2- A As a computer that is used to build that originally operated primarily under. Although it is a powerful general-purpose programming language, it was primarily used to construct /business programs. Clipper was originally released in 1985 as a for III, a very popular database language at the time. DBASE code changes it from interpreted code, which must be every time each line of code is executed, to, which uses a to process the compiled p-code. P-code is considerably faster, but still not as fast as the generated by native compilers.
As a technical marketing ploy, the p-code was wrapped into object code (linkable.obj files) which gave the impression that it was compiled to native code. Clipper was created by led by Barry ReBell (political) and Brian Russell (technical), and later sold to. Licensed CA-Clipper in 2002 from CA for ongoing marketing and distribution.
As the product matured, it remained a tool for many years, but added elements of the and, as well as, and the code-block (hybridizing the concepts of dBase, or -evaluation, and ), to become far more powerful than the original. Nantucket’s Aspen project later matured into the native-code compiler. After “swallow” Nantucket at 1992, CA published a few releases of Clipper Compiler, lastly 5.3a at May 20, 1997. But most of Clipper programmer uses preferably 5.2e – released February 7, 1995. Although remained a as the compiler, Clipper continues to live as the programming language. The Clipper language is being actively implemented and extended by multiple organizations/vendors, like from Alaska Software and, as well as (-licensed) projects like.
Many of the current implementations are portable (, ( and ), (32- and 64-bit), and ), supporting many language extensions, and have greatly extended, as well as various Replaceable Database Drivers (RDD) supporting many popular database formats, like, DBTNTX, DBFCDX (, Apollo and Comix), MachSix (SIx Driver and Apollo), and more. These newer implementations all strive for full compatibility with the standard / syntax, while also offering OOP approaches and target-based syntax such as SQLExecute.