Hi
Cyril,
In
theory it should work, as it's just some Java code, similar to that produced by
ESQL. The disadvantage, is that you don't have any error checking or logging to
fall back on when situations like this occur, and ESQL would provide
that.
Anyway, the only obvious thing that I can see, is to put \\'s in your connection string, e.g:
("jdbc:odbc:localhost:8080/c:\\Mes_documents\\JAVA\\JDBC\\logs");
Also
turn on ODBC tracing and see if any other information is logged, to help you
resolve the problem.
Perry
|
- Cocoon 2 + Access cyril vidal
- Re: Cocoon 2 + Access Torsten Curdt
- Re: Cocoon 2 + Access Andrew C. Oliver
- Re: Cocoon 2 + Access Faulkner, Perry
- Re: Cocoon 2 + Access cyril vidal
- RE: Cocoon 2 + Access Christopher Watson
- Re: Cocoon 2 + Access:it runs now well... cyril vidal
- RE: Cocoon 2 + Access Faulkner, Perry
- Re: Cocoon 2 + Access Tom Klaasen
- Re: Cocoon 2 + Access Bert Van Kets
- Re: Cocoon 2 + Access cyril vidal
- Re: Cocoon 2 + Access Tom Klaasen