P
Pete_UK
Now, now. Don't get personal !! <bg>
Pete
Pete
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
jkend69315
Pete, still monitoring this thread? I'm wondering why you chose to
return to using a regular xls format for your file over the exe. Was
it the additional overhead or what? We're so excited about the
xls-to-exe conversion that we've ordered a new computer to try it
without risking any loss of work or Windows problems on our existing
computers before downloading. We have a lot of work involved here, so
we're being extra careful! If workable, this thing could be BIG for
all of us VBA programmers. Any further comments from anyone would be
appreciated. James
return to using a regular xls format for your file over the exe. Was
it the additional overhead or what? We're so excited about the
xls-to-exe conversion that we've ordered a new computer to try it
without risking any loss of work or Windows problems on our existing
computers before downloading. We have a lot of work involved here, so
we're being extra careful! If workable, this thing could be BIG for
all of us VBA programmers. Any further comments from anyone would be
appreciated. James
P
Peter Noneley
James,
I'm not sure what is exciting you most:
(a) The Excel Function Dictionary
or
(b) The converter from XLS to EXE
I can take credit for (a) as I slogged away at that.
I can't take credit for (b) as I downloaded that from Orlandos web
site.
The reason I went back to XLS was because of the way EXE seemed to
'hide' any macro code from Excel when the worksheet opens up. With an
XLS Excel should pop up the old "Enable/Disbale macros" box, but with
the EXE that was not happening.
A lot of people are dubious of anything that does not warn them and
then give them choice of whether to run the macro or not.
Also I have not investigated the EXE version to find out if there are
conflicts with Functions or features, although I think one difference
in the EXE is that it can disable the File,SaveAs command.
Would like to hear what you would do with the EXE converts.
Peter
Cardiff (Veeeerrrryyyyyy wwwwwiiinnndyyyy and wet)
Wales
UK
I'm not sure what is exciting you most:
(a) The Excel Function Dictionary
or
(b) The converter from XLS to EXE
I can take credit for (a) as I slogged away at that.
I can't take credit for (b) as I downloaded that from Orlandos web
site.
The reason I went back to XLS was because of the way EXE seemed to
'hide' any macro code from Excel when the worksheet opens up. With an
XLS Excel should pop up the old "Enable/Disbale macros" box, but with
the EXE that was not happening.
A lot of people are dubious of anything that does not warn them and
then give them choice of whether to run the macro or not.
Also I have not investigated the EXE version to find out if there are
conflicts with Functions or features, although I think one difference
in the EXE is that it can disable the File,SaveAs command.
Would like to hear what you would do with the EXE converts.
Peter
Cardiff (Veeeerrrryyyyyy wwwwwiiinnndyyyy and wet)
Wales
UK
B
Bob Phillips
Peter,
I think the big deterrent is not that they don't get any warning, but that
it just opens an Excel workbook with macros without any warnings. In
reality, an executable can do just as much damage as an Excel workbook with
macros, but there is a credibility disconnect. I like to think I am a
relatively sophisticated user, but it took me aback somewhat.
Regards
Bob
I think the big deterrent is not that they don't get any warning, but that
it just opens an Excel workbook with macros without any warnings. In
reality, an executable can do just as much damage as an Excel workbook with
macros, but there is a credibility disconnect. I like to think I am a
relatively sophisticated user, but it took me aback somewhat.
Regards
Bob
J
jkend69315
Thanks for replying, Peter. I think I like the exe for the very reason
some people object to it. I have a very involved VBA program and I
want to protect the code from piracy. Evidently, if the user can't see
the code, that is some protection for me. Also, there seems to be some
effort to keep the file from being easily copied. I like that, too.
As to the macro warning, if macros are not enabled on my file, the user
will not get any benefit from using it, so I don't see much difference
in whether the warning shows or not. The user will know that the
program contains code before he opens it, so he has the option of just
not using it if that's a problem. According to Orlando, the original
xls can remain intact without interference from the exe, so the
original file remains available for editing (by me!). Regards, James
some people object to it. I have a very involved VBA program and I
want to protect the code from piracy. Evidently, if the user can't see
the code, that is some protection for me. Also, there seems to be some
effort to keep the file from being easily copied. I like that, too.
As to the macro warning, if macros are not enabled on my file, the user
will not get any benefit from using it, so I don't see much difference
in whether the warning shows or not. The user will know that the
program contains code before he opens it, so he has the option of just
not using it if that's a problem. According to Orlando, the original
xls can remain intact without interference from the exe, so the
original file remains available for editing (by me!). Regards, James
P
Peter Noneley
James,
I'm not sure the EXE actually hides the code. I have only skimmed the
surface of the converter, but I think it works by storing the original
XLS in the EXE and then creates a copy of the XLS in Excel. It is a bit
like having a template.
The duplicate copy of the XLS will still have the macro code in it.
Well I think that is what happens.
If any one really knows, could they please explain.
If I get time over the weekend I will send a mail to Orlando and ask
him!
Peter Noneley
Cardiff (Dry and cold)
Wales
UK
www.xlfdic.com
I'm not sure the EXE actually hides the code. I have only skimmed the
surface of the converter, but I think it works by storing the original
XLS in the EXE and then creates a copy of the XLS in Excel. It is a bit
like having a template.
The duplicate copy of the XLS will still have the macro code in it.
Well I think that is what happens.
If any one really knows, could they please explain.
If I get time over the weekend I will send a mail to Orlando and ask
him!
Peter Noneley
Cardiff (Dry and cold)
Wales
UK
www.xlfdic.com
A
aaron.kempf
you know.. if you DIPSHITS kept your data in a DATABASE then you could
reuse it in 100 different ways.
Excel is a dead end street.
Anyone that uses it for anything-- should be fired and then spit upon.
-Aaron
reuse it in 100 different ways.
Excel is a dead end street.
Anyone that uses it for anything-- should be fired and then spit upon.
-Aaron
P
Peter Noneley
All,
It looks like Aaaron has got the wrong end of the stick here. But I
guess this may also be a good time to call an end to this thread.
If anything major pops up on the subject of XLS and EXE then I will
write it up in a new thread.
Bye.
Peter
Cardiff (Sunny but cold)
Wales
UK
www.xlfdic.com
It looks like Aaaron has got the wrong end of the stick here. But I
guess this may also be a good time to call an end to this thread.
If anything major pops up on the subject of XLS and EXE then I will
write it up in a new thread.
Bye.
Peter
Cardiff (Sunny but cold)
Wales
UK
www.xlfdic.com
A
aaron.kempf
eat a dick blimey
spreadsheets are for fucking idiots that don't have the mental capacity
to learn a real tool-- like a database or crystal reports for that
matter
-Aaron
spreadsheets are for fucking idiots that don't have the mental capacity
to learn a real tool-- like a database or crystal reports for that
matter
-Aaron
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.