Help getting an old program to work

[imported_Phil]

Hi all,

At the company I work for, we use a program called Gemini Plus, which ties in with Gemini, the call-logging system we use. The person that wrote Gemini Plus as an addon to Gemini is no longer with the company and we can't contact him.

When trying to load the program on a fresh machine with XP Pro, it gives errors with missing .ocx files. So, I copied the related files over and registered them manually. However, now I'm getting this error message:

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Now, I know vaguely what that means, but I'm not a database guy and therefore have nooo idea how to solve it.

The strange thing is, that my boss' machine (which is also running XP Pro), was upgraded from a WinNT 4 installation, and runs this program fine. I've checked his Data Sources control panel applet, and there's a buttload of stuff in there and I'm not sure which entries to replicate on my machine to try and get the program working.

Can anyone offer some help as to what sources or files this program is trying to open and failing? I'm stuck and we could reeeeally use this program!

Cheers

 

[WannaFly]

if you dont know wish specific DSN, copy them all.

 

[EagleKeeper]

The program is looking for a ODBC (database) driver interface that is a registered name. without it, the program can not find the related "database".

Look at all the ODBC connections on the bosses system that have an Access interface.

Look at the properties. They will point to a database that is being referenced. Therre may also be some parameters in the advanced options.

All that information will need to be placed onto the virgin system.

This is why is is benificial to always install a probam on a virgin system (that the developer has not touched) to determine what items are assumed and/or have been tweaked and not documented.

 

[imported_Phil]

Thanks for the pointers guys. I figured out that it was the Syteline connection that it was missing, as it ties into that system (oops, d'oh).

Anyway, upon creating the connection, I tried the program again. This time it gave a runtime error 3706, which I traced to it needing the MDAC components or VB Runtimes. I installed both, and now I have the following message:

[INTERSOLV][ODBC PROGRESS driver]Optional feature not implemented.

I should point out that the settings I have copied from the working system are identical to those on my system, so I can't see how this kind of message can appear.

Any further ideas?

Thanks

 

[imported_Phil]

bump

 

[imported_Phil]

I've done some ODBC tracing, and have some log files if someone would be kind enough to look at them? One's pretty large (26 pages of text) from the working system, one's six pages from the non-working system.

I have a vague idea of why it's stopping, but my knowledge of SQL is limited at best and I could do with someone experienced giving me a few pointers!

Cheers guys

 

[imported_Phil]

Bump for help!

 

[Fritoz]

Ghost your boss' hard drive? (Minus any private files, natch...)

 

[imported_Phil]

Originally posted by: Fritoz
Ghost your boss' hard drive? (Minus any private files, natch...)

Minus private files, you say? Hmm, an interesting concept...

But still, we'd like to find out what it is that XP lacks and XP-upgraded-from-NT4 has that makes this program work.

 

[imported_Phil]

DP

 

[imported_Phil]

bump

 

[MrChad]

You might not have the right ODBC driver installed. It sounds like the application is trying to use an Intersolv driver to connect to a Progress datasource. Does that match how the NT machine is setup (i.e. is the NT datasource configured the same way)?