> Yeah, that is true, for example, with one odbc pointing to and mdb for
> example you cannot do this: rs.getString(1) and after try to do it again,
> you must do TYPE x = rs.get<TYPE>(n); and read x the times you want but no
> read a column more than once from Query...
That's really bizar... And that sucks. Where does this limitation come from?
The driver? Access? Would this alternative syntax:
String x = getString(String columnName)
do the same thing? Where could i find a list of these "bugs"/limitations.
And what about a driver of type IV, would there be the same limitations?
I must confess you that I am a bit discouraged. They wont buy SQL server.
And they dont want to change neither their damn it NT OS nor their IIS
server. I am familiar with macosX/BSD+Apache+PHP, but I hoped I could use
JSP instead of ASP to do the server-side job and to interact with their
Access db... but I dont like this story of restrictions.
If you want to make someone happy and you already made a successful web app
using JSP interacting with an Access Database in a NT environment, please
conact me !!!
[EMAIL PROTECTED]
Otherwise, is there free&efficient alternatives to Acces on NT? mySQL is
free for all plateform i think, but will the integration with JSP be easier?
thank you very much guys
>
> Guido.
>
> ----- Original Message -----
> From: "Alexandre Bouchard" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 24, 2001 2:46 PM
> Subject: Re:Re: JDBC/ODBC: Technological choice
