Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Problem with macros
Options
Go to last post Go to first unread
Previous Topic Next Topic
benmcgiffin  
#1 Posted : Wednesday, December 17, 2014 10:02:17 PM(UTC)
benmcgiffin
Rank: Newbie

Reputation:

Groups: Registered
Posts: 2

I have been using ESdat 5 with no problems however now when ever I create a chem output table, most of macros no longer work. The export to pro UCL macro still works, but the the formating buttong (change colour, bold exceedences ect) does not work and some of the statistics are not showing up. Has anybody encountered this problem before?

I'm using excel 2013 however I have saved the output file and tryed to open in 2010 versions with no sucess 

Cheers

Ben

Back to top

Wanna join the discussion?! Login to your ESdat Forums forum accountor Register a new forum account.
Back to top  
Warwick Wood  
#2 Posted : Thursday, December 18, 2014 1:27:32 AM(UTC)
Warwick Wood
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 498
Man
Location: Byron Bay

Was thanked: 19 time(s) in 19 post(s)

Hello Ben,

We've had some other users report this.  The guys at Monarc Environmental had the problem first and were good enough to send us the solution to share.  Please see their advice below.

 

Just to let you know...we resolved the issue with ESdat on Friday night. A Microsoft Office update early last week had rendered ActiveX controls useless as per the excelmatters.com website link I sent you. The upshot is that two temp files had to be deleted see below. Once these had been deleted ESdat worked straight away. You might want to add this fix to the FAQs or something.

C:\users\username\AppData\Local\Temp\Excel8.0\MSForms.exd
C:\users\username\AppData\Local\Temp\VBE\MSForms.exd

http://excelmatters.com/2014/12/10/office-update-breaks-activex-controls/

and here: http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/11/forms-controls-stop-working-after-december-2014-updates-.aspx 
Back to top
WWW
benmcgiffin  
#3 Posted : Thursday, December 18, 2014 10:02:33 PM(UTC)
benmcgiffin
Rank: Newbie

Reputation:

Groups: Registered
Posts: 2

Thanks Warwick

 

After removing the files, ESdat and excel were back to normal 

 

Cheers

 

Ben

Back to top
Tom Wilson  
#4 Posted : Tuesday, December 23, 2014 10:04:05 PM(UTC)
Tom Wilson
Rank: Advanced Member

Reputation:

Groups: Registered
Posts: 39
Location: Ballina
Further to this, Microsoft has released a Fix It: http://support.microsoft.com/kb/3025036/EN-US
Tom Wilson Senior Implementation Manager EarthScience Information Systems (EScIS)
Back to top
Cheaying  
#5 Posted : Saturday, April 2, 2016 12:08:13 AM(UTC)
Cheaying
Rank: Newbie

Reputation:

Groups: Registered
Posts: 1
I had this problem before and got it fixed by removing the 2 “Msforms” files as above.
 
Now I’m running Windows 10 and office 2010, this problem resurfaces. I deleted the file but every time I try to export ESdat chemical table, the “Msforms”  file within C:\users\...\appdata\local\temp\excel8.0 creates by itself again and this stops the format exceedances from working.
 
I’ve installed the excel security updates from here https://support.microsoft.com/en-us/kb/3025036 but it doesn’t seem to resolve the issue? Can you shed some lights here?
Back to top
Warwick Wood  
#6 Posted : Wednesday, April 6, 2016 4:00:10 AM(UTC)
Warwick Wood
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 498
Man
Location: Byron Bay

Was thanked: 19 time(s) in 19 post(s)

Hi Cheaying,

If it has just started happening, I'd suggest roll back any Office updates.  We've not heard anything beyond what is in this forum, but we'd appreciate any experiences anyone has with this.

Warwick 

 
Back to top
WWW
FMG-sysadmin  
#7 Posted : Thursday, April 7, 2016 7:31:32 PM(UTC)
FMG-sysadmin
Rank: Newbie

Reputation:

Groups: Registered
Posts: 2

Hi Warwick,

 I'm the Sys Admin at FMG and am responsible for rolling out software company wide which includes Cheayings machine.

At the moment we're rolling out Office 2013 in order to bring our staff closer to the current century. As our clients upgrade their software, so must we; and by not upgrading our software we are not able to utilize current libraries that have been developed by other clients.

I've made the decision to move her forward to 2010 so she can run other macros; unfortunately this leaves ESdat as the only application that doesn't conform to more modern technology.

 The package looks like it does work with 2010 from what I've seen and going back to 2007 seems like an easy out...

 The reason it has only just started happening is because it has only just been installed.

Do you have any technical based solutions to this problem? (I've done over a decades worth of application support and can code a bit)

 

Regards,

Duvall 
Back to top
Warwick Wood  
#8 Posted : Saturday, April 9, 2016 10:19:31 PM(UTC)
Warwick Wood
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 498
Man
Location: Byron Bay

Was thanked: 19 time(s) in 19 post(s)

Hi,

Just confirming that ESdat works fine on Office 2010 and Office 2013 (32 and 64 bit), and most of our users are on those versions.  The first time this was identified (see first post) was actually on 2010.    

Last time this occured (as documented above) it was identified as a bug in an Office patch, which affected Excel in general (ie not just ESdat), the only resolution was to roll back that office patch, until Microsoft issued a fix, which they did (see above).  While obviously this is a major issue for us, and our users, we can't control this kind of issue (in the immediate term at least), so the only technical based solution is to try applying the Office patch, or update Office to the latest version, or if the issue persists after that, to roll back any Office patches that were applied post installation.  

Regards,

Warwick 

 

Edited by user Saturday, April 9, 2016 10:36:33 PM(UTC)  | Reason: Not specified
Back to top
WWW
FMG-sysadmin  
#9 Posted : Wednesday, April 13, 2016 8:58:42 PM(UTC)
FMG-sysadmin
Rank: Newbie

Reputation:

Groups: Registered
Posts: 2

Thanks for the response, Warwick.

 I've managed to fix the problem.

 

By uninstalling Microsoft Office 2010 Service Pack 2 Update, it now works. 
Back to top
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2024, Yet Another Forum.NET