|
Thanks for the reply Rich; Thom responded
yesterday too. Maybe I should just direct these to support for now since you
have released the product, and let them filter out what needs your attention. As you see from my question, I am still
stuck with the idea of file handles. Although I understand the concepts, I
haven’t worked with OOP enough to be aware of all it offers. It is like
when I started programming in C a decade or so ago; there were functions to do
stuff that you usually programmed, but you have to know they are there. Same
with OOP for me; I didn’t realize that there was a property (D.EOF) to test my while loop with. I was still trying to
figure out the handle. Comes with experience, I guess. Seems I
spend more time now-a-days researching for methods and properties for things I
could have written in about the same amount of time I spent looking. Of course,
there is the payoff that next time I know it is there. By the way, now that I am getting the hang
of BDS, it is very cool. I look at what I was trying
to do as far as record parsing, and the BDS library
handles so much of what I used to have to code. Kudos to you and BSS for a good addition
to your toolset! Lew Hundley -----Original Message----- Lew, The DataStation is meant
to make file handling as simple and straightforward as possible so a lot of
VB’s arcane requirements just don’t apply. If you need to access another file, you
can open another DataStation object with, say, Dim
D1 as New DataStation And then use: D1.Open
“filename”, ftWhatever -----Original Message----- If I want to write a loop for a
Meditech Magic script to look for EOF, I do something like this While Not EOF(1) Where 1 was used to open the file Open FileName As #1 and is a unique identifier of the
file (you don’t have two files open at the same time as 1) Now, in C/S I need to write a loop
using the new DataStation, so the code generated by BWS is D.Open_ “C:\SOMEFILE” ,
ftFixedLength where ftFixedLength is system
defined as the number 2. Assuming the same logic is used for the While While Not EOF(ftFixedLength) doesn’t this mean that if I
wanted to have 2 fixed length files open at the same time (say, transferring data
to two file at the same time, that I would have to change the tool-generated
ftFixedLength of the second file that I want to open to some other number? I just want to clarify that I
understand the use of ftFixedLength in the D.Open_ statement, since both files
could be fixed length files, but the number has to be unique. This may be a
stupid question, but I just want to be sure that I understand. TKs for indulging me, DISCLAIMER: |
- [Talk] BWS question for Meditech C/S Lew Hundley
- RE: [Talk] BWS question for Meditech C/S Thom C. Blackwell
- RE: [Talk] BWS question for Meditech C/S Rich McNeil
- Lew Hundley
