November 29, 2021, 05:13:18 PM

News:

Due to SPAM attacks, new members must be approved before posting.  Please email jclough@warrenpinnacle.com when registering and your account will be approved.


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - SteveF

1
Using SLAMM / Re: Run Time Errors
October 27, 2014, 09:47:09 AM
Quote from: Jonathan S. Clough on October 27, 2014, 06:29:41 AM
Try un-checking the box to write to MS Word -- J



It has not been checked in any of the runs I've initiated.
2
Using SLAMM / Re: Run Time Errors
October 25, 2014, 08:07:32 AM
I am using Windows 7.0 and Office 2010. Both are paid versions that were installed when I purchased my Toshiba Laptop.  The computer has a Core i7, Service Pack 1, 8.00 GB RAM,

I am using Version 6.2 Beta downloaded within 1 week.  When I launch SLAMM, its banner reads SLAMM v6.2 beta, December 2012, 64 bit.

When I start the simulation, using the sample data you provided (both the S1_puget Sound and Stmarks_SLAMM_6.2) two pop up windows appears: 

The first
Microsoft Visual Basic error, Run-time error '429': ActiveX component can't create object

The Second
Runtime Error copying map to Microsoft Word for year 0. Retry writing map to Word?

The first time I ran the model, I did not see the check box for saving maps to GIF format.  The second time, I did check the box.   However the error occurred in each circumstance.  I am not modifying anything except the length of time the model runs, instead of running to 2100, I selected 2020 with a 10 year time step, just to put the model through its paces.

I'll continue to test, but I don't know where to look, any suggestions are greatly appreciated.
3
Using SLAMM / Run Time Errors
October 24, 2014, 10:34:32 AM
Hello,  I am new to SLAMM modeling and am just starting to learn how it works.  My first adventure starts with a 'Run Time Error '429' message.  ActiveX component can't create object."

I see that this relates to the Visual Basic DLL.  I am using Windows 7.0 and Office 2010.  Where should I look to fix this?

Thanks
Steve