s3pe Error

[Martine]

Yesterday I was using s3pe, when all of sudden I got these error messages:

http://i33.tinypic.com/288y5ie.png

The program continues to work fine, but I get these errors when opening a package, saving it, etc. etc. I have to click the continue button a few times and then it works.

I've just installed the latest version of both s3pe and s3oc. I have the required network thing installed. When I try to install the net framework again (as it seems that is the problem causer), the installation fails. I currently have .NET Framework 3.5 SP1 installed, but I'm afraid that if I uninstall this, and the installation fails again, I won't be able to use s3pe anymore.

Anyway, not sure what caused this, and the error message is getting on my nerves, so I was hoping someone could help.

[Inge Jones]

Can you tell me if it occurs just in specific packages, or all packages? If it's just specific packages, please can you give me an example package to test with? Thanks.

[Martine]

It's the same for all my packages :(

[Inge Jones]

So you think this was caused by installing the latest versions of the tools - it started as soon as you did that, and not before?

[Martine]

No it started before, I reinstalled to see if that would fix the problem. I remember editing a package in s3pe, and I accidently clicked the IsDeleted column when trying to sort the parts of the package differently, and then I got the first error.

[Inge Jones]

Ok so on one occasion you clicked the "IsDeleted" column, and after that, everything you open gives this error? Have you rebooted your computer since this began?

[Martine]

Sorry I meant to add more, as I was editing my post the forum wouldn't load anymore.

I did reboot several times since the first error. All the packages gave that error after the first one. Also, I can click on all columns to change the sorting manner normally, except for IsDeleted, that one continues to give me the error (as well as almost every other action; saving, opening, importing, exporting).

[pljones]

I've "fixed" this in the latest release... by disabling sorting on the endmost column. It's a hack until I work out how to do it properly.