SuccessMaker Application Conflict

[Midget]

After battling with this PoS for quite a while I have now finally discovered that the reason it will not work is down to an application conflict.

 

I did a clean install of XP and installed SM, and it worked, however after all the programs that are installed by the GP had installed it did not.

 

It seems to be caused by one of the following:

 

Adobe Acrobat 7.07

Adobe Flash player

Sun Java 1.5

MS Office 2000

MS Visual Basic 6

2Connect (some software for GCSE ICT)

 

What do you think is the most likely cause before I have to reinstall windows several times over trying to find the culprit?

[Geoff]

I'd suspect VB6. Successmaker is probably written in some other flavour of VB.

[plexer]

I'd suspect vb6 too.

 

Ben

[Midget]

ok then, i'll try vb6 as the first suspect then.

 

I have no idea what to tell the computing teacher who teaches VB6 to his ALevel kids.

 

Apart from my previous hinting that we should be using VB.net since we have a licence for it - he's never used it himself, so requires more training to teach it....apparently.

 

As we'll be changing to Office2003 this year they have no excusses about VB6 working better with Access2000

[plexer]

How many machines do you have Successmaker licensed for then as last time I looked it was bloody expensive?

 

Ben

[Midget]

Oh its still bloody expensive, but as we were upgrading we only had to buy 25 licences @~£180ea to get a site licence.

[Midget]

well done geoff and plex you were right, just tried installing VB6 and SM stopped working. Before I reimage the machine and try it, what are the odds that VB.net will produce the same fault?

[Geoff]

Should work ok.

[plexer]

It's probably some runtime dll's or something that are getting overwritten and then being the wrong ones for successmaker.

 

Ben

[Geoff]

DLL hell basically.

[Midget]

which is wierd because if you install vb6 first and THEN successmaker it still doesnt work (and the ODBC install fails)

[john]

Give RM a poke, they should be able to solve this as people are still using VB 6 and they should really look at it rather than force an update to vb.net