Issue 76822 - in vba compat mode class modules are not processed correctly
Summary: in vba compat mode class modules are not processed correctly
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: OOo 2.2 RC4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.4
Assignee: sled10guy
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-01 18:50 UTC by noel.power
Modified: 2009-07-20 14:53 UTC (History)
1 user (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
patch file (753 bytes, patch)
2007-05-01 18:52 UTC, noel.power
no flags Details | Diff
test document (24.50 KB, application/vnd.ms-excel)
2007-05-01 18:53 UTC, noel.power
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description noel.power 2007-05-01 18:50:41 UTC
when class modules are imported from excel the correct mode 'option classmodule'
needs to be set for the module
adding to cws npower7
Comment 1 noel.power 2007-05-01 18:51:23 UTC
adjust milestone
Comment 2 noel.power 2007-05-01 18:52:37 UTC
Created attachment 44789 [details]
patch file
Comment 3 noel.power 2007-05-01 18:53:19 UTC
Created attachment 44790 [details]
test document
Comment 4 noel.power 2007-05-05 13:15:59 UTC
fixed
Comment 5 noel.power 2007-07-11 12:50:15 UTC
for qa
Comment 6 noel.power 2007-08-07 10:18:06 UTC
change target
Comment 7 sled10guy 2007-08-28 16:23:51 UTC
Ran test document (simpleclass.xls) on released SLED10 SP1 OOo 2.1.14, Windows
OOo 2.1 (Build 2007-06-04) and cws-npower7-m217. In each case the following
output was displayed in a msgbox when the "Run Classmodule Test" button was pushed:
• oSim.OrderID 1
• oSim.CustomerName Fred
• oSim.Value 100.2000
‣ In the case of Microsoft Office 2007,  the following output was displayed in a
msgbox when the "Run Classmodule Test" button was pushed:
• oSim.OrderID 1
• oSim.CustomerName Fred
• oSim.Value 100.2
‣ RESULT: So the oSim.Value precision was different for Microsoft Office then it
was for OOo. I'm not sure if this is bad, but it was the only difference I was
aware of during the testing.
Comment 8 thorsten.ziehm 2009-07-20 14:53:16 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues