Well, if you've been using Clarion 5 a bit, you probably have a good
idea of what might be useful to convert. I think you'll probably find
that, though some of the DOS code still runs, that you are better off
rewriting it using the ABC cl*****: in general this will involve
writing much less code than you used to have, which will save
maintenance costs down the road. Code that might make sense to bring
over is stuff that defines a transaction, although in converting to a
"proper" database you will probably want to convert these to stored
procedures on the database. Also, in the conversion to a database you
should change all your process procedures to SQL statements --
actually that applies to most things that loop through "records".
It depends on your app what code you might end up with from what you
have in Clarion for DOS, but I'd suggest that it would be very little
- less than 5%.
Jon
On Apr 24, 7:51 am, Clara <mareli...@[EMAIL PROTECTED]
> wrote:
> Hi.
> We're currently working on Clarion 5 for windows and clarion for DOS
> (mostly the latter).
>
> We're using I.S. files for our data and we'd like to upgrade to a
> relational db, upgrading the clarion version as well (6 or 7).
>
> Is there anyone who already worked on a ****ting like this? We'd like
> to know, if there's any chance to use/convert our code or if we have
> to write totally new code. And if we can use it, do you know, in your
> experience, what's the percentage of code able to be upgraded?
>
> Thanks in advance for any help.
> clara
|
