Re: VBA and VSTO
- From: "Jos Vens" <jos.vens@xxxxxxxxxxxxxx>
- Date: Sun, 2 Apr 2006 03:26:34 +0200
Hi Bob,
you can try it yourselve: I stripped a lot of code and placed it on my
website. You can download Libra and extract it. You start it up with
Libra.xls which opens Libra.xla in the Programma folder. It is compiled with
office 2000 first release, so in that case, it does not crash (in office
2000, it never crashes on any servicepacks)
So the assumption of 100 modules is not right here, because I deleted many
modules and almost all forms. Maybe something must be corrupted but the
CleanProject did not resolve anything...
http://www.puntenboek.be/Download/Crash.zip
Jos
"Bob Phillips" <bob.phillips@xxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:uRLlf$eVGHA.4952@xxxxxxxxxxxxxxxxxxxxxxx
If that is the case, you should be able to strip it down to something much
simpler than causes these crashes. Could you do that and then offer the
code
for review?
--
HTH
Bob Phillips
(remove nothere from email address if mailing direct)
"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message
news:us7irJeVGHA.4764@xxxxxxxxxxxxxxxxxxxxxxx
Thank you all for your reactions. Let's explain a bit more:If
I just tried Bob's method: I opened my application in Office 2000 first
edition. Compiled it. Worked fine.
Then I opened it in office XP, crashed on startup.
I think Bob means: all commands of 2000 will work on XP and 2003. Yes, I
know, but thats not the problem. I use only 2000 commands. The problem is
the compilation. If I migrate from 2000 to XP or 2003, my compilation is
gone. I know that because if I open the VBE-environment, the menu-item to
compile is black, not greyed out, saying my project is not compiled yet.
I compile then, It works fine.I
What have I figured out by now: it is the mso.dll that causes the
problem.
build my menubar on startup, and there it crashes. If I use the mso.dllfrom
the excel version I have compiled with (by replacing the installed one),compile,
I
have no problem.
I know my project loses it compilation if it encounters another mso.dll.
I
also know that if I forget to compile, my project crashes. So If I
and go to another excel-version, compilation is gone and my projectcrashes.
now
Thanks, more suggestions are welcome!
Jos Vens
"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> schreef in bericht
news:uvxoCCcVGHA.5900@xxxxxxxxxxxxxxxxxxxxxxx
I know,
but if VSTO is stable, I can convince my customers to migrate to 2003,
unlessit's a mess: my excel application crashes on almost every machine,
SP3).it is upgraded to the right version (like for XP is it 10.6789.6735
compilerAll other versions are crashing, unless I recompile. I've built a
but(I use the sendkeys method to unlock the project etc etc... It worked,
(.exe)on 2003 I couldn't save it anymore - an error on saving appeared for an
unknown reason).
Thanks for all your suggestions!
Jos Vens
"Bob Phillips" <bob.phillips@xxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:eIFbDYbVGHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
If you are deploying to Excel 2000 and Xp as well as 2003, VB.Net
isn't
really an option anyway.
--
HTH
Bob Phillips
(remove nothere from email address if mailing direct)
"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message
news:O1B0EUbVGHA.736@xxxxxxxxxxxxxxxxxxxxxxx
Hi Chip,from
I mean, I developped in VBA, and I don't want to spend to much time
to
set
my code in vb.net. Is the language comparable or do I have to learn a
lot
(and debug a lot) to get my code back in vb?
I never used VB.NET! I assume you mean I cannot copy and paste my
code
vba to vb.net.
Jos
"Chip Pearson" <chip@xxxxxxxxxxxx> schreef in bericht
news:uuJmpPYVGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Assuming you know VB.NET,
1. Is my code in VBA in a high level portable to the new platform
Only you can answer that question.
2. Can I compile the project to an executable stand-alone file
VSTO.so
I am not dependent to what the user have installed of dll's
With VTSO, you end up with a workbook and a managed code DLL.
3. Does it work with all versions of Office (starting with 2000)
No. 2003 only.
--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com
"Jos Vens" <jos.vens@xxxxxxxxxxxxxx> wrote in message
news:ubE1QEYVGHA.5020@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
since I have serious problems in VBA, I consider to migrate to
(.exe)I
have some questions about that, in order of importance:
1. Is my code in VBA in a high level portable to the new platform
2. Can I compile the project to an executable stand-alone file
muchso
excelI am not dependent to what the user have installed of dll's
3. Does it work with all versions of Office (starting with 2000)
Thanks for your help.
Jos Vens
PS my big problem in VBA is the difference of the mso.dll
(mso9.dll
for
office 2000) of the different office versions, which causes a
crash
on
startup when I build up my menu-bar. Recompilation on the specific
version solves the problem, but then I have to maintain at least 3
versions (2000, XP and 2003). Even subversions (Service Packs and
minor
upgrades cause those commilation problems so I cannot keep that
versions).
.
- Follow-Ups:
- Re: VBA and VSTO
- From: RB Smissaert
- Re: VBA and VSTO
- From: RB Smissaert
- Re: VBA and VSTO
- From: Bob Phillips
- Re: VBA and VSTO
- References:
- VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Chip Pearson
- Re: VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Bob Phillips
- Re: VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Jos Vens
- Re: VBA and VSTO
- From: Bob Phillips
- VBA and VSTO
- Prev by Date: Re: VBA and VSTO
- Next by Date: Re: Setting Range in Graph
- Previous by thread: Re: VBA and VSTO
- Next by thread: Re: VBA and VSTO
- Index(es):
Relevant Pages
|
Loading