Good to hear.

Trent,

It's working now on my test machine.

thanks,
Mark

I have sent you the license file via email.

Yeah, the license file is tied to the MAC address so it would require another license.  If you just go into the license activation client there is a link for a manual activation and it will appear at the proper location so we can get you the file.

Sorry, I just realized I needed a new license file. I sent Jay the info via email, wasn't sure how to contact you directly.

thanks,
Mark

I installed VS 2005 and Strataframe on a new test machine. I used the same "MicroFour License.dll" file as on my other machine. It took the file and said it was sucessfully activated, but when I started VS I got a string of errors, see attached.

thanks,
Mark

Mark,

It doesn't happen very often, but I missed this post.  Sorry

Just so that we might be able to move time to the left here...do you have another machine, test or otherwise, that you can load SF on so that we can see if you have the same issue?  When you get this error, and we have catches everywhere, VS DTE likes to snuff the errors, so it is difficult to troubleshoot.  But the issue isn't always an SF issue and other plug-ins can have an affect on what happens since we are tying into the VS IDE.  This might help us figure out what is cropping up in this environment.

I compiled and ran the multicolumn combo sample with success. I see both StrataFrame and StrataFrameSample databases on my sql server. Attached is the log.

Apparently you didn't get my PM the other day   I never heard back from you so that is why I did not post here on this thread again.

Ignore the error for a minute and let's see if you can open one of the sample projects and compile it.  Next, let's see if you have a StrataFrame database on the server that you choose to install.  You can open the log files in the c:\program files\common files\MicroFour\StrataFrame folder.  They will be called

StrataFrame_Results.log and StrataFrameSample_Results.log

Let's look to see if there were any errors.  I know that you have something in your environment that is causing the issue, and since we have tried all of the stuff that generally causes this issue we can start to dig around.

I'm willing to keep trying if you'd like to give me some more items to look at.

thanks,

Mark