I can think of a few ways;
First use an editor to pre-process the file and search/replace the ~ with
CR/LF
You can also process it character by character and format it that way, slow
but it works
You may be able to fool the import by changing the end of record delimiter
to '~' but not sure if you can do that, at least not in gateway, thats a
Razzak question
Not sure if something like excell will take the ~ either
 
 
 
Mark Lindner
Lindner & Associates PC
254 Second Ave
Needham MA  02494
781 247 1100
Fax 781 247 1143
 
 

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen
Sent: Wednesday, June 09, 2010 12:41 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - File Load



Group,
 
I had created an EDI load process for a client a couple of years ago. The
client decided
to change their edi provider (you can see where this is going).
 
The old files looked like this
ISA*00*          *00*          *08*9254110060     *12*9933358077
*091229*0431*U*00307*000001932*0*P*>~
GS*RA*5137624388*9933358077*20091229*0431*1932*T*004010UCS~
 
The new format looks like this (it may wrap weird). Basically it comes in
one long line.
ISA*00*          *00*          *08*9254110060     *12*9933358077
*091229*0431*U*00307*000001932*0*P*>~GS*RA*5137624388*9933358077*20091229*04
31*1932*T*004010UCS~
 
It appears that there is a line end character of ~.
 
My old routine took advantage of a line never being more than 120 characters
wide.
It simply did a
LOAD tEDILoad FROM .vFileName AS FORMATTED USING EDIRawLoad 1 120
 
Once I can get the file into R:BASE, I'm pretty sure that the original
routine will work.
 
I'm drawing a blank as how to load this file.
 
This is in an older version of 7.6 (don't ask).
 
Jan

 

 

-----Original Message-----
From: "Mike Byerley" <[email protected]>
To: [email protected] (RBASE-L Mailing List)
Date: Wed, 9 Jun 2010 10:49:54 -0400
Subject: [RBASE-L] - Re: OLE 2 in rbase ?


I would guess that the EfilmObj is an ActiveX viewer.
You could convert your VB code to VBScript with no difficulty, since late 
binding is the method of Object creation and simply call the VBS file from 
RBase using the "Launch" command.  To take it a step further, you can store 
the VBS file in a VarChar data field in the database and retrieve it, write 
it to disk and run it, deleting it after the run, to keep the file from 
anyone fooling with the source code.

If you aren't familiar with scripting, the main difference in VBScript is 
all variables are Variants, so when you do variable declaration, you omit 
the "as DataType" assignment.


----- Original Message ----- 
From: "Luc Delcoigne" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, June 09, 2010 10:18 AM
Subject: [RBASE-L] - OLE 2 in rbase ?


Hello again,

in the database that I am converting from Access to R:BAse 9.0 we have a 
procedure that links our database with Efilm X-ray filmviewer.

This is the procedure :

Public Sub Efilm()
Dim EfilmObj As Object
Dim var As Boolean
Dim varefilm As Boolean
Dim vpatID As String, vcon As String, bCloseCurWindow As Boolean, 
bAddToWindow As Boolean, nSeriesRows As Integer, nSeriesCols As Integer, 
nImageRows As Integer, nImageCols As Integer, bAutoSeriesFormat As Boolean, 
bAutoImageFormat As Boolean
Set EfilmObj = CreateObject("Efilm.Document")

    vpatID = Forms![InterfaceNieuw]![Patiƫnten].Form![Punieknummer]
     vcon = Forms![InterfaceNieuw]![Consultatie].Form![Consultnummer]
    bCloseCurWindow = True
    bAutoSeriesFormat = False
    bAutoImageFormat = False
    nSeriesRows = 1
    nSeriesCols = 2
    nImageRows = 1
    nImageCols = 1
    varefilm = EfilmObj.oleOpenStudy(vpatID, vcon, bCloseCurWindow, 
bAddToWindow, nSeriesRows, nSeriesCols, nImageRows, nImageCols, 
bAutoSeriesFormat, bAutoImageFormat)

varefilm = EfilmObj.oleSetForegroundWindow

End Sub


How could I get the same functionality in R:base to link to Efilm and 
automatically open all the required film-documents based on the 
'Punieknummer' and the 'Consultnummer' ?

Many, many, many thanks

;-)

Luc Delcoigne 


 

Reply via email to