Difference between VM Classpath and SC.ini Classpath

[Holger Wiechert]

Hi,

we just had a nice "yeah" about a little strange thing. I want to post it
here
since I think that it might help others as well.
We use VC3.0c Pro with the VM 1.2.2. I still don't know, if we ran
into this problem since we used some Oracle stuff, but I really don't think
so.
I think it's rather a VC thing. But here's the story:

We tried to load the Oracle Light's JDBC driver (of the OLITE40.jar) by
Class.forName("oracle.lite.poljdbc.POLJDBCDriver");

The OLITE40.jar was in the SC.ini classpath list, let's say
C:\O_Resources\OLITE40.jar. But we got the
exception: java.lang.ClassNotFoundException:
oracle.lite.poljdbc.POLJDBCDriver
(we also tried to unjar the file).

Just after including the path (C:\O_Resources\OLITE40.jar)
to the VM's classpath via Tools->Environment Options...
->Register "Virtual Machines" -> VM 1.2.2 (which we installed before) ->
Modify ->
Classpath (classpath for use by the VM executable), it worked fine.

My question is: what is the difference between those two classpath settings?

Thanks in advance.

Regards, Holger

[Tim Dutton (Symantec)]

I have forwarded your message to the more appropriate newsgroup below.

symantec.support.itools.win.vcafe3.database

You can find your question and any response there.

If you came in through the web interface what you need to do is go to
the following web page and under the Visual Cafe 3.0 drop down list
select DATABASE QUESTIONS and then click the Browse button. The
message will have my name on it.
http://www.symantec.com/techsupp/vcafewin/ask_vcafewin.html

==========================================================

Regards,

Tim Dutton
Internet Tools Technical Support
Symantec Corporation

[Symantec/Ted Flug]

Holger

When using a plugged in VM the sc.ini file is ignored during
compilatin, executing and debugging.

Ted Flug
Symantec Internet Tools