Hello Thomas,

seems to be a very weird configuration problem, but relatively hard
to check from the remote.

So, there are not so many options that remain:

 - Check that the 'java' exe called at your command line is the program you wanted.
   (And not an older, or other version, or perhaps from some other vendor ... e.g.
    the Microsoft JVM)

 - Try 'java -jar sapdbc.jar -V', this should print some version number. If not, 
   the jar is perhaps somehow corrupted - get it again at the web site.

 - Put the sapdbc.jar in another path, and try it there. Perhaps there is something
   wrong in the file system.

> When I try to compile:
>      Class.forName ("com.sap.dbtech.jdbc.DriverSapDB");
> I get:
>      java.lang.ClassNotFoundException
> 

*Compiling* this should work, if the JDK is correctly installed. *Compiling*
does not check for the argument of Class.forName. So even Class.forName("foobar") 
should compile without any problems. 

> Strangely enough I am able to import the lib, like:
>      import com.sap.dbtech.jdbc.*;
> 

This does not import anything, so if you want make a real check, 
make an 

  import com.sap.dbtech.jdbc.DriverSapDB

to check.

Regards
Alexander Schr�der
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to