Depends which forum you're in. Some of the NGs you get bi*** slapped for
not answering in-line. I don't mind writing at the top though.
----- Original Message -----
From: "Dennis McGrath" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, March 10, 2010 12:09 PM
Subject: [RBASE-L] - Re: OT (Sort of) : [RBASE-L] - Re: Reports to Excel
Mike,
When you respond, could you put your answer at the top of the email?
It is much easier to find that way, and is standard email practice these
days.
Thanks :)
Dennis McGrath
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of MikeB
Sent: Wednesday, March 10, 2010 10:58 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: OT (Sort of) : [RBASE-L] - Re: Reports to Excel
----- Original Message -----
From: <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, March 10, 2010 11:10 AM
Subject: [RBASE-L] - Re: OT (Sort of) : [RBASE-L] - Re: Reports to Excel
You lit a fire, Mike! Even if I don't use this for this application, I
think
I will dust this off and play around with it! Thanks for the sample code,
but it appears to NOT be ascii text, I get binary characters. Is that
right?
No. I just looked at the text file (which I had annotated in Notepad) and
it was as you described. I resaved it again, reopened it in notepad and it
is still TEXT, so check your inbox again.
Karen
In one of my Word apps, I connect to RBase for an envelope addressing
program.
I am going to email you the VBA code to connect to an RBase db, set a
recordset, etc. You can glean from that enough to get you started.
When you are in the VBA editor in Excel, find the Object Viewer. It will
list all the properties and methods of the Spreadsheet which will give
you
clues about how to go about manipulating your data.
This incident is another reason I have encouraged people to grasp at
least
VBScript as a useful tool as it is basically a subset of VB5/VB6 from
which
VBA is based. Almost all of the language constructs are interchangable.
In our (I mean the developer community at large) there are few times that
the data doesn't become entwined with Microsoft Office products at some
point, so the above advice will likely hold true for some time. I know
MS
has experimented with using Dot Net as the basis for Office products, but
to
date it has failed miserably due to its' cumbersome size which translates
to
snail pace performance.
