Clarion - Apps, etc., being made available

Author

Apps, etc., being made available

Dan Pressnell

2006-03-04, 6:55 pm

Hello, everybody.

I am in the process of putting together some packages of the tools (classes,
templates, etc.) I've made and uploading them to Icetips.com.

I've got two upladed already, so they should be available soon:

1. BetterSQLandOOPforClarion55.zip -- this contains the files that went
with the Better SQL and Better OOP series of articles.

2. dp_Class Template Setup.zip -- This contains a small template that makes
it possible to edit your *.inc, *.clw, and *.int class files in the Clarion
IDE, so that they are generated along with the app and saved with the app.

In the near future, I'll be making packages for twTools and twMySQL and
uploading them as well, and I'm placing them in the public domain.

Dan

David Troxell - Encourager Software

2006-03-04, 6:55 pm

In article <Y9nOf.54694$g47.41789@tornado.tampabay.rr.com>, dp@nospam.com
says...
> Hello, everybody.
>
> I am in the process of putting together some packages of the tools (classes,
> templates, etc.) I've made and uploading them to Icetips.com.

Dan,

Thanks for all your hard work over the years and sharing generously with the
Clarion community - may you be rewarded with plenty of PAID consulting <g>!

And especially thanks for all the SQL articles
(http://www.icetips.com/articles.php?articlecategory=1) you have
contributed, and thanks to Arnor for maintaining these.

David

>
> I've got two upladed already, so they should be available soon:
>
> 1. BetterSQLandOOPforClarion55.zip -- this contains the files that went
> with the Better SQL and Better OOP series of articles.
>
> 2. dp_Class Template Setup.zip -- This contains a small template that makes
> it possible to edit your *.inc, *.clw, and *.int class files in the Clarion
> IDE, so that they are generated along with the app and saved with the app.
>
> In the near future, I'll be making packages for twTools and twMySQL and
> uploading them as well, and I'm placing them in the public domain.

That is a very generous offer as well! Thank you!

David

>
> Dan
>
>
>

--
From David Troxell - Product Scope 32 PRO - Encourager Software
Email - mailto:C3P_Remove_@_Me_encouragersoftwar
e.com
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/

Earl R Coker

2006-03-04, 9:55 pm

Hi Dan,

I have a very special request for you but first let me explain my position
on the subject.

I am going to have to start working with an MS-SQL version of one of my apps
very soon now. I know almost nothing about doing anything with SQL. IOW, I
will end up with two "versions", one existing .tps version and one SQL
version using ODBC.

I read your articles when you first put them together, and even read them
again about a month ago, but I was not able to get much of what "I" needed
out of them. <g> The reason being, for the most part, I did not know
"what" you were talking about most of the time. e.g. what the SQL "terms"
meant etc... etc... IOW, your explanations talked about "things" I have no
"background" understanding of when reading them. I have read other
information put forth by people on the newsgroup and ClarionMag but, even
after all that reading, I have not been able to learn, step-by-step, how to
install and use an SQL app "from scratch".

It seemed to me you (and the others) were writing these articles for someone
that already at least had some basic understanding of SQL terminology and
SQL's idiosyncrasies. <g>

What I need is:
1.) A very concise (e.g. not real "wordy") but complete step-by-step guide
on how to:
a.) Install MS-SQL (including versions and their ideosyncracies) on a
MS 2000 Terminal Server.
b.) Install the apps and database.
c.) Set up the Client(s).
d.) Connect to and use a CW app.
e.) A glossary of terms used in the guide.

Using an MS-SQL database.

This is kind of difficult for me to even explain since I know so little
about even what is required to get the job done. <g> When I say, "concise
(not real "wordy")" I mean that when it's done, please give just a short
explanation and then along with the explanation, give some "examples and/or
prototypes" for doing it. By the time I "plow" through all of the verbage
in most of what I have found so far on the subject, my mind goes into
"neutral" and I don't really "learn" anything. <g>

Here is a suggested format for the Quick Reference Guide I am talking
about... e.g. the Step-By-Step Guide Format...

1.) What this step is (does), (Example: Install MS-SQL)
a.) Sub-Step Concise explanation of Step 1.).
A.) Sub-Step of 1a if needed.
B.) Concise explanation of Sub-Step 1aA. if needed.
b.) Sub-Step Why this step is needed.
A.) Sub-Step of 1b if needed.
B.) Concise explanation of Sub-Step 1bA. if needed.
c.) Sub-Step Where this step is implemented.
A.) Sub-Step 1c if needed.
B.) Concise explanation of Sub-Step 1cA. if needed.
d.) Sub-Step How this step is implemented.
A.) Sub-Step of 1d if needed.
B.) Concise explanation of Sub-Step 1dA. if needed.
e.) Sub-Step Code prototype if needed.
A.) Sub-Step of 1e if needed.
B.) Concise explanation of Sub-Step 1eA. if needed.
2.) What this step is (does),
a.) Sub-Step Concise explanation of Step 2.).
A.) Sub-Step of 2a if needed.
B.) Concise explanation of Sub-Step 2aA. if needed.
b.) Sub-Step Why this step is needed.
A.) Sub-Step of 2b if needed.
B.) Concise explanation of Sub-Step 2bA. if needed.
c.) Sub-Step Where this step is implemented.
A.) Sub-Step of 2c if needed.
B.) Concise explanation of Sub-Step 2cA. if needed.
d.) Sub-Step How this step is implemented.
A.) Sub-Step of 2d if needed.
B.) Concise explanation of Sub-Step 2dA. if needed.
e.) Sub-Step Code prototype/example if needed.
A.) Sub-Step of 2e if needed.
B.) Concise explanation of Sub-Step 2eA. if needed.

Continue on with as many "What, Why, Where, How, and Prototype/Example
Steps" in the above format as necessary. You can even do a copy-and-paste
of the above "format" as a way of providing a guide for doing it and then
just "fill in" the steps that are necessary and just add some necessary
steps and/or steps or delete the un-necessary steps and/or sub-steps.

1.) Install MS-SQL
a.) To install the database system.
A.) Step of 1a if needed.
B.) Concise explanation of Sub-Step 1aA. if needed.
b.) Why this step is needed.
A.) Step of 1b if needed.
B.) Concise explanation of Sub-Step 1bA. if needed.
c.) Where this step is implemented:
A.) Sub-Step 1c if needed.
B.) Concise explanation of Sub-Step 1cA. if needed.
C.) Sub-Step 1c if needed.
D.) Concise explanation of Sub-Step 1cC. if needed.
d.) Sub-Step How this step is implemented.
A.) Sub-Step of 1d if needed.
B.) Concise explanation of Sub-Step 1dA. if needed.
e.) Sub-Step Code prototype if needed.
A.) Sub-Step of 1e if needed.
B.) Concise explanation of Sub-Step 1eA. if needed.
2.) What this step is (does),
a.) Sub-Step Concise explanation of Step 2.).
A.) Sub-Step of 2a if needed.
B.) Concise explanation of Sub-Step 2aA. if needed.
b.) Sub-Step Why this step is needed.
A.) Sub-Step of 2b if needed.
B.) Concise explanation of Sub-Step 2bA. if needed.
c.) Sub-Step Where this step is implemented.
A.) Sub-Step of 2c if needed.
B.) Concise explanation of Sub-Step 2cA. if needed.
d.) Sub-Step How this step is implemented.
A.) Sub-Step of 2d if needed.
B.) Concise explanation of Sub-Step 2dA. if needed.
e.) Sub-Step Code prototype/example if needed.
A.) Sub-Step of 2e if needed.
B.) Concise explanation of Sub-Step 2eA. if needed.

I will be more than happy to be a "beta tester" <g> for whatever you come up
with. I will even use Help&Manual to make an eBook of it for you. <g>

--
Best Regards,
Earl R Coker
ksasales AT machlink DOT com
kwiksys AT kwiksystems DOT net
www.kwiksystems.net
www.kwiksystems.com
www.kwiksystems.net/appshell/index.htm
www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)

"Dan Pressnell" <dp@nospam.com> wrote in message
news:Y9nOf.54694$g47.41789@tornado.tampabay.rr.com...
> Hello, everybody.
>
> I am in the process of putting together some packages of the tools
> (classes, templates, etc.) I've made and uploading them to Icetips.com.
>
> I've got two upladed already, so they should be available soon:
>
> 1. BetterSQLandOOPforClarion55.zip -- this contains the files that went
> with the Better SQL and Better OOP series of articles.
>
> 2. dp_Class Template Setup.zip -- This contains a small template that
> makes it possible to edit your *.inc, *.clw, and *.int class files in the
> Clarion IDE, so that they are generated along with the app and saved with
> the app.
>
> In the near future, I'll be making packages for twTools and twMySQL and
> uploading them as well, and I'm placing them in the public domain.
>
> Dan
>
>

Dan Pressnell

2006-03-05, 3:55 am

Hi, Earl.

Are you expecting this by tomorrow? :)

Don't worry too much about SQL challenges in Clarion. Discussion of SQL
seems difficult, but that's only because it tends to center on a relatively
few things that stand out as differences in how you program in Clarion. I
may be guilty myself of misleading, in that in my articles I tended to focus
on that "different" way of doing things, and I'm afraid I made it sound like
EVERYTHING had to be different. There are even some things in my articles
on SQL that I now wish I hadn't said or hadn't emphasized so much.

I can assure you that 95-99% of what you do in Clarion with SQL will be
exactly the same as you would do with TPS files, unless you are deterimined
to do something very weird.

I believe that the lack of "knowledge" on how do "do SQL" in Clarion is an
essential part of the perception that Clarion is a lightweight language. If
you know how to deliver a robust, bullet-proof application to access an SQL
database in Clarion, no programmer in any other language can touch you in
the category of quality and speed of development. It's not the language
that creates an inadequate program, it's all the programmer's fault. But
business executives will always blame the language if it's not Microsoft, it
seems.

I'll be putting together some more how-to's. I'll focus on starting from
scratch--no dictionary, no app, no database, go from there. I'm thinking of
using Camtasia to make video walkthroughs and give them away, but I haven't
decided whether to spend that much money yet on something that won't make a
penny for me. (What will my wife think!)

Dan

"Earl R Coker" <ksasales AT machlink DOT com> wrote in message
news:120kmcm3u89un81@corp.supernews.com...
> Hi Dan,
>
> I have a very special request for you but first let me explain my position
> on the subject.
>
> I am going to have to start working with an MS-SQL version of one of my
> apps very soon now. I know almost nothing about doing anything with SQL.
> IOW, I will end up with two "versions", one existing .tps version and one
> SQL version using ODBC.
>
> I read your articles when you first put them together, and even read them
> again about a month ago, but I was not able to get much of what "I" needed
> out of them. <g> The reason being, for the most part, I did not know
> "what" you were talking about most of the time. e.g. what the SQL "terms"
> meant etc... etc... IOW, your explanations talked about "things" I have
> no "background" understanding of when reading them. I have read other
> information put forth by people on the newsgroup and ClarionMag but, even
> after all that reading, I have not been able to learn, step-by-step, how
> to install and use an SQL app "from scratch".
>
> It seemed to me you (and the others) were writing these articles for
> someone that already at least had some basic understanding of SQL
> terminology and SQL's idiosyncrasies. <g>
>
> What I need is:
> 1.) A very concise (e.g. not real "wordy") but complete step-by-step guide
> on how to:
> a.) Install MS-SQL (including versions and their ideosyncracies) on a
> MS 2000 Terminal Server.
> b.) Install the apps and database.
> c.) Set up the Client(s).
> d.) Connect to and use a CW app.
> e.) A glossary of terms used in the guide.
>
> Using an MS-SQL database.
>
> This is kind of difficult for me to even explain since I know so little
> about even what is required to get the job done. <g> When I say,
> "concise (not real "wordy")" I mean that when it's done, please give just
> a short explanation and then along with the explanation, give some
> "examples and/or prototypes" for doing it. By the time I "plow" through
> all of the verbage in most of what I have found so far on the subject, my
> mind goes into "neutral" and I don't really "learn" anything. <g>
>
> Here is a suggested format for the Quick Reference Guide I am talking
> about... e.g. the Step-By-Step Guide Format...
>
> 1.) What this step is (does), (Example: Install MS-SQL)
> a.) Sub-Step Concise explanation of Step 1.).
> A.) Sub-Step of 1a if needed.
> B.) Concise explanation of Sub-Step 1aA. if needed.
> b.) Sub-Step Why this step is needed.
> A.) Sub-Step of 1b if needed.
> B.) Concise explanation of Sub-Step 1bA. if needed.
> c.) Sub-Step Where this step is implemented.
> A.) Sub-Step 1c if needed.
> B.) Concise explanation of Sub-Step 1cA. if needed.
> d.) Sub-Step How this step is implemented.
> A.) Sub-Step of 1d if needed.
> B.) Concise explanation of Sub-Step 1dA. if needed.
> e.) Sub-Step Code prototype if needed.
> A.) Sub-Step of 1e if needed.
> B.) Concise explanation of Sub-Step 1eA. if needed.
> 2.) What this step is (does),
> a.) Sub-Step Concise explanation of Step 2.).
> A.) Sub-Step of 2a if needed.
> B.) Concise explanation of Sub-Step 2aA. if needed.
> b.) Sub-Step Why this step is needed.
> A.) Sub-Step of 2b if needed.
> B.) Concise explanation of Sub-Step 2bA. if needed.
> c.) Sub-Step Where this step is implemented.
> A.) Sub-Step of 2c if needed.
> B.) Concise explanation of Sub-Step 2cA. if needed.
> d.) Sub-Step How this step is implemented.
> A.) Sub-Step of 2d if needed.
> B.) Concise explanation of Sub-Step 2dA. if needed.
> e.) Sub-Step Code prototype/example if needed.
> A.) Sub-Step of 2e if needed.
> B.) Concise explanation of Sub-Step 2eA. if needed.
>
> Continue on with as many "What, Why, Where, How, and Prototype/Example
> Steps" in the above format as necessary. You can even do a
> copy-and-paste of the above "format" as a way of providing a guide for
> doing it and then just "fill in" the steps that are necessary and just add
> some necessary steps and/or steps or delete the un-necessary steps and/or
> sub-steps.
>
> 1.) Install MS-SQL
> a.) To install the database system.
> A.) Step of 1a if needed.
> B.) Concise explanation of Sub-Step 1aA. if needed.
> b.) Why this step is needed.
> A.) Step of 1b if needed.
> B.) Concise explanation of Sub-Step 1bA. if needed.
> c.) Where this step is implemented:
> A.) Sub-Step 1c if needed.
> B.) Concise explanation of Sub-Step 1cA. if needed.
> C.) Sub-Step 1c if needed.
> D.) Concise explanation of Sub-Step 1cC. if needed.
> d.) Sub-Step How this step is implemented.
> A.) Sub-Step of 1d if needed.
> B.) Concise explanation of Sub-Step 1dA. if needed.
> e.) Sub-Step Code prototype if needed.
> A.) Sub-Step of 1e if needed.
> B.) Concise explanation of Sub-Step 1eA. if needed.
> 2.) What this step is (does),
> a.) Sub-Step Concise explanation of Step 2.).
> A.) Sub-Step of 2a if needed.
> B.) Concise explanation of Sub-Step 2aA. if needed.
> b.) Sub-Step Why this step is needed.
> A.) Sub-Step of 2b if needed.
> B.) Concise explanation of Sub-Step 2bA. if needed.
> c.) Sub-Step Where this step is implemented.
> A.) Sub-Step of 2c if needed.
> B.) Concise explanation of Sub-Step 2cA. if needed.
> d.) Sub-Step How this step is implemented.
> A.) Sub-Step of 2d if needed.
> B.) Concise explanation of Sub-Step 2dA. if needed.
> e.) Sub-Step Code prototype/example if needed.
> A.) Sub-Step of 2e if needed.
> B.) Concise explanation of Sub-Step 2eA. if needed.
>
> I will be more than happy to be a "beta tester" <g> for whatever you come
> up with. I will even use Help&Manual to make an eBook of it for you. <g>
>
> --
> Best Regards,
> Earl R Coker
> ksasales AT machlink DOT com
> kwiksys AT kwiksystems DOT net
> www.kwiksystems.net
> www.kwiksystems.com
> www.kwiksystems.net/appshell/index.htm
> www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)
>
>
>
> "Dan Pressnell" <dp@nospam.com> wrote in message
> news:Y9nOf.54694$g47.41789@tornado.tampabay.rr.com...
>
>

Earl R Coker

2006-03-05, 6:55 pm

Hi Dan,

Thanks for the quick reply.

> Are you expecting this by tomorrow? :)

No but you seem to know a lot about it so I would think you could "bang it
out" rather quickly. <g>

> Don't worry too much about SQL challenges in Clarion. Discussion of SQL
> seems difficult, but that's only because it tends to center on a
> relatively few things that stand out as differences in how you program in
> Clarion.
Clarion apps using .tps files are so easy to develop, install and use,
especially by small businesses with "very" limited "computer experience", is
my take on what you are saying. The "biggie" reason for using SQL seems to
be file corruption but NONE of my customers have EVER had a file corruption
problem that was NOT caused by a hardware problem. Of course the other
reason is the size of the data in the database but that is not a concern of
mine.

> There are even some things in my articles on SQL that I now wish I hadn't
> said or hadn't emphasized so much.

Along this same line, I looked at the "print book" that is for sale by
ClarionMag as a possibility for a reference guide for doing what I want.
It's 600 or more pages. akkkk... Waaay overkill for what I need
"information" wise. However, I guess I could use it as reference material
while using the quick reference guide if necessary. Although I did look at
the table of contents and the index and it does seem to be pretty well
organized.

> I can assure you that 95-99% of what you do in Clarion with SQL will be
> exactly the same as you would do with TPS files, unless you are
> deterimined to do something very weird.

Yes, I am aware of that. All of my apps are "standard" Clarion with no
"wierd" stuff at all in them that I am aware of. I think they will work
just fine in SQL after "conversion".

> I'll be putting together some more how-to's. I'll focus on starting from
> scratch--no dictionary, no app, no database, go from there.

That's even more than I am asking for. I am not interested in doing any
apps from scratch. I will already have the existing ".tps app" converted to
SQL. I just need to have a "how-to" quick reference guide for installing
MS-SQL on a PC, then installing the apps, making the connections, and a
discussion about any ideosyncracies with respect to using the system. There
seems to be quite a bit of newsgroup chatter about doing the "SQL thing"
here lately so I think this kind of a quick reference guide would be well
received.

> I'm thinking of using Camtasia to make video walkthroughs and give them
> away, but I haven't decided whether to spend that much money yet on
> something that won't make a penny for me. (What will my wife think!)

This is a good idea but I think doing it would be a much bigger job than
what I am asking for.

--
Best Regards,
Earl R Coker
ksasales AT machlink DOT com
kwiksys AT kwiksystems DOT net
www.kwiksystems.net
www.kwiksystems.com
www.kwiksystems.net/appshell/index.htm
www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)

David S. Beggs

2006-03-06, 3:55 am

Earl,
Capesoft have a pretty good explanation as part of the FM3 docs
http://www.capesoft.com/docs/fm3/fm3sql.htm
Cheers!
Dave Beggs
--
www.dsbglobal.com/d-icons
900 icons for $10

"Earl R Coker" <ksasales AT machlink DOT com> wrote in message
news:120ltk6cu3lia7e@corp.supernews.com...
> Hi Dan,
>
> Thanks for the quick reply.
>
>
> No but you seem to know a lot about it so I would think you could "bang it
> out" rather quickly. <g>
>
> Clarion apps using .tps files are so easy to develop, install and use,
> especially by small businesses with "very" limited "computer experience",
> is my take on what you are saying. The "biggie" reason for using SQL
> seems to be file corruption but NONE of my customers have EVER had a file
> corruption problem that was NOT caused by a hardware problem. Of course
> the other reason is the size of the data in the database but that is not a
> concern of mine.
>
>
> Along this same line, I looked at the "print book" that is for sale by
> ClarionMag as a possibility for a reference guide for doing what I want.
> It's 600 or more pages. akkkk... Waaay overkill for what I need
> "information" wise. However, I guess I could use it as reference material
> while using the quick reference guide if necessary. Although I did look
> at the table of contents and the index and it does seem to be pretty well
> organized.
>
>
> Yes, I am aware of that. All of my apps are "standard" Clarion with no
> "wierd" stuff at all in them that I am aware of. I think they will work
> just fine in SQL after "conversion".
>
>
> That's even more than I am asking for. I am not interested in doing any
> apps from scratch. I will already have the existing ".tps app" converted
> to SQL. I just need to have a "how-to" quick reference guide for
> installing MS-SQL on a PC, then installing the apps, making the
> connections, and a discussion about any ideosyncracies with respect to
> using the system. There seems to be quite a bit of newsgroup chatter
> about doing the "SQL thing" here lately so I think this kind of a quick
> reference guide would be well received.
>
>
> This is a good idea but I think doing it would be a much bigger job than
> what I am asking for.
>
> --
> Best Regards,
> Earl R Coker
> ksasales AT machlink DOT com
> kwiksys AT kwiksystems DOT net
> www.kwiksystems.net
> www.kwiksystems.com
> www.kwiksystems.net/appshell/index.htm
> www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)
>
>
>

Earl R Coker

2006-03-06, 6:55 pm

Hi Dave,

Thanks for the link. I think I can get going from that info as it seems to
cover most, if not all, of the things I was asking about. Of course, I will
need to purchase FM3 which I haven't done yet which is probably the reason I
did not know about that link. I went to the Microsoft SQL web site and it
tells there now to install their SQL stuff.

It seems to me that SQL is a lot more difficult to implement and use than
Clarion .tps stuff. And for the small business, SQL is IMNSHO overkill.

Thanks again.

--
Best Regards,
Earl R Coker
ksasales AT machlink DOT com
kwiksys AT kwiksystems DOT net
www.kwiksystems.net
www.kwiksystems.com
www.kwiksystems.net/appshell/index.htm
www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)

"David S. Beggs" <dosprinter@nospam.dsbglobal.com> wrote in message
news:ZRROf.2848$z03.785@news-server.bigpond.net.au...
> Earl,
> Capesoft have a pretty good explanation as part of the FM3 docs
> http://www.capesoft.com/docs/fm3/fm3sql.htm
> Cheers!
> Dave Beggs
> --
> www.dsbglobal.com/d-icons
> 900 icons for $10
>
>
> "Earl R Coker" <ksasales AT machlink DOT com> wrote in message
> news:120ltk6cu3lia7e@corp.supernews.com...
>
>

Sponsored Links