×
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.
Is there any difference between creating a physical source file member
and compiling it versus using an SQL CREATE TABLE command? When using
the i5, I've always created a PF and then compiled it as my table, but I
have never created a table using the SQL CREATE TABLE command.
I did a test of the CREATE TABLE command, and it did indeed create a PF
in the specified directory. However, it doesn't create the associated
member (or does it?) that I can use to modify and update the table if
fields need to be added/modified/deleted.
One advantage I did notice is that I am not limited to ten characters
like a standard physical file (yes, I understand there are ways around
it).
Are there any specific reasons why I would want to select one method
over another? File maintenance would be a matter of editing the PF
member and doing a CHGPF on a modified file versus an ALTER TABLE
command.
Am I missing something fundamental here?
Thanks!
/b;
-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.