I'll have to third that sentiment.  avoid jdbc-odbc unless you
absolutely have no other choice.

Access is fine for light weight database, but once the database starts
to grow, be aware that indexes start to fail miserably. I don't know if
the latest version has the same problems of the past, but I do know
everything from office 1997 and older starts to have index problems at
around 200K+ records.  This is from first hand experience and
tribulations of friends who develop database application in access and
foxpro.

it might be more work to change the database for the webapp, but it
might save you more time down the line.

peter



Larry Meadors wrote:
> 
> I will second this - do not use the jdbc-odbc bridge unless you
> absolutely have to.
> 
> If there is ANY other path, take it instead.
> 
> Larry
>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to