plz help.
shital
You can't create an exe from an Excel file or macro. You could replicate
what your file does in VB and create an application from VB, but that is a
lot of work, depending on the functionality.
HTH,
Bernie
"shah" <shahs...@rediffmail.com> wrote in message
news:060301c30996$bf92a8f0$a501...@phx.gbl...
Depending on what the macro does, another route might be rewriting it as
VBScript and saving it in a .VBS file.
--
Public Service Announcements:
1. Don't attach files to postings in this newsgroup.
2. Learn how to snip unnecessary text from quoted material. Indiscriminate
quoting wastes more bandwidth than file attachments.
Actually,you can,although not from within Excel of course.
Have you ever heard of a spreadsheet compiler? I have a DOS
version of an application called BALER that creates a
runtime executable of a spreadsheet file.
Biff
>.
>
And Baler was written how long ago? Can it handle XLS files, especially Excel 97
and later XLS files? Can it handle *macros* written in VBA that make use of
Excel's object model?
If your interested:
http://the-ciba.com/vbaler/vbaler.html
Biff
>-----Original Message-----
>"Biff" wrote...
>>Actually,you can,although not from within Excel of
course.
>>Have you ever heard of a spreadsheet compiler? I have a
DOS
>>version of an application called BALER that creates a
>>runtime executable of a spreadsheet file.
>...
>
>And Baler was written how long ago? Can it handle XLS
files, especially Excel 97
>and later XLS files? Can it handle *macros* written in
VBA that make use of
>Excel's object model?
>
>--
>Public Service Announcements:
>1. Don't attach files to postings in this newsgroup.
>2. Learn how to snip unnecessary text from quoted
material. Indiscriminate
> quoting wastes more bandwidth than file attachments.
>.
>
And a little digging leads to
http://the-ciba.com/vbaler/support/sales.html#converting
which states:
"What is involved in converting my spreadsheet to Visual Baler.
Converting from another spreadsheet to Visual Baler is dependent on what is in
your spreadsheet and where it is coming from. If you spreadsheet is originally
in Lotus 2.4 (WK3) format and macros the conversion will be quite straight
forward. If you are coming from Excel/Quattro Pro - then you must save the file
as a WK3 prior to loading it in VB and you will most likely have to rewrite all
the macro code. If you are coming from a DOS baler product with a WK1 file then
your formulas will be fine, but any macro's written with slash (/) commands will
have to be rewritten. Also template tables are not supported in the Visual Baler
product."
So . . . if you convert your Excel workbooks to Lotus 123's .WK3 format, meaning
any and all array formulas would be toast along with any functions not built
into 123R3, anything below row 8192 in any worksheet and any descriptive
worksheet names, rewrite all Excel macros (both VBA *and* XLM) in Lotus 123
Release 2.4 macro language (I have to believe they mean 123R3+ macro language,
but maybe they mean what they say), then you can convert your spreadsheet to a
16-bit executable that you very likely won't be able to run in the next version
of Windows.
SUCH A DEAL!
Granted, converting existing files involves some work, but
you can start with a clean slate and develope the
application entirely within Baler. The OP's question was:
Can I create an EXE file ? The answer is:
Yes
or
Yes,but.........
Biff
>-----Original Message-----
>"Biff" wrote...
>>If your interested:
>>
>>http://the-ciba.com/vbaler/vbaler.html
>...
>.
>
Of course if the OP starts from scratch *and* has some tool capable of
generating EXE files he can create EXE files. The question is whether it's
practical or worthwhile to use Baler to create a functional work-alike for
an Excel workbook.
I guess you just don't understand what the OP wrote. I'll refresh your
memory.
shah wrote . . .
>...>i have created a macro. i want to copy that into my home
>...>computer. i can use copy & paste file into computer. but
>...>how can i create a "exe" file of my prog. file. or a setup
>...>file.
Baler doesn't support even the XLM macro language. So to use Baler, the
first step would be to translate the (presumably) VBA macro into 123R2 or
123R3 macro language. Do you have any clue what that involves? If you're
going to have the OP translate the macro into some other language, why on
earth have them target a system that can only create 16-bit applications?
The work involved in translating Excel files with macros into a form Baler
can handle is prohibitive. Have you done much 'porting' back & forth between
123 classic and either XLM or VBA? It'd be faster, easier and more
OS-compatible for the OP to buy Visual Basic and a spreadsheet control. This
is especially true because Baler is no longer actively developed or
supported.
If the OP's real problem is that he created an XLS file at work but doesn't
have Excel at home, then buying Excel 97 or 2K from an auction site would
make much more sense than buying Baler and would cost less. If the OP wanted
to distribute an EXE to others, Baler make no sense going forward because of
the 16-bit issue.
So yes, BUT! Like saying if I can just stay healthy, I can live to 110.
Whether it's practicle or worthwhile is for the user to
decide. Of course the points you raise should be taken
into consideration. Right now, today, would I choose
Baler? Maybe, maybe not. It depends. What am I trying to
accomplish ? What tools are available ? Are my skills up
to the task ? Who will use this and under what conditions ?
Years ago, I asked myself the same question as the OP's.
My curiosity led me to Baler.
Biff
>.
>