Setting up a datasource for a text file (directory actually (similar to
Paradox)) is not a big deal. You can have a schema.ini file (made upon
creation and design of the DSN) in the directory that the textfile resides
in to define a layout and field names for the file. If you don't use a
schema.ini file, then you can still access each field position by names like
F1, F2, F3, etc...
Here is a sample JOIN query that can be used on text files (file1.txt has
field definitions and is fixed-width, file2.txt is comma delimited and has
no field definitions):
SELECT
b.*, a.*
FROM
file2.txt As a
INNER JOIN
file.txt As b
ON
Left(b.SLLS, 6) = Left(Cstr(a.F1), 6)
hth...
David L. Penton, MCP
Consultant
"Mathematics is music for the mind, and Music is Mathematics for the
Soul. - J.S. Bach"
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Jean
I have NO idea how to write a query on a comma delimited list. I know
that a txt file can be a datasource, but what are the limitations on
the setup of the file itself, registering the datasource, and querying
it? The extent of use that we will have from this file are selects and
select where -blank- starts with "R" etc.
=====
Veni, Vedi, Velcro.
I came, I saw, I stuck with it.
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org
