×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Adam
This is a really broad and vague question - what language will it be
written in? Which RDBMS will be used (Oracle, SQL Server, etc.)? Web app
or local app? Will it be talking to the i, or is the i being replaced? I
don't know, all kinds of questions.
SQL is SQL is SQL, for the most part. There will be some syntax
differences, but, as Charles said, simple things are the same. You need
to adjust for whatever flavor of SQL you use for some things - for data
types, e.g. Another example is, on the i you can use substr() - on SQL
Server you have to use the entire word substring() - that also works on
the i, so if you want portability, you use the whole word.
Stored procedures could be an issue, but I doubt you are going that way.
They are the "programs" of SQL database systems.
We have a product, a software development kit, actually - that lets you
work real-time with other SQL database systems - not a plug - heh. The
thing is, I have to find the right syntax for those other systems. For
SQL Server I will use what used to be called the Query Analyzer - it's
part of their management interface now. I try something, I test, I read
the help text, I get the answers.
HTH
Vern
Adam West wrote:
IF you had to be converting an application from the i to a windoze box, how would you convert if any changes necessary to your SQL? Assuming of course the files are mapped in some way. I am interested in any major or minor issues you have noticed.
Thank you,
Adam
midrange.com
