From: Paul Smith <paul@...>
Date: 2009-10-27T23:53:51+09:00
Subject: Re: SQL Shell for MS Access

>> Maybe this is the right way to go, I just really like the command
>> line, as I'm used to working with mysql, and there you can just fire
>> up mysql-client, get a mysql> prompt, and start typing things like
>> show tables to list all the tables in the db, desc table to describe
>> the layout of a given table.
>
> You could as well try a generic DB client (e.g. SQirreL) which should
> also be capable of making use of Access's ODBC driver via the JDBC
> ODBC bridge (although that is not perfect as well).  Maybe there's
> also a native Windows ODBC SQL client around that you could use.

I'll keep on investigating.  So close, but yet so far.

>
>> I'm just trying to make working with MS Access feel more like working
>> with mysql :)
>
> Seems like you are forced to work with MS Access.  I would try to
> avoid it if possible. :-)

I would too :)  I'm maintaining a database as a bit of a side job at
work, and it's currently in MS Access.  There's no real reason I guess
to keep it in MS Access, other than I may have to pass it on to
someone else at a later date, and they're more likely to have some
Access knowledge than anything else.

If it was my main job I'd probably spend the effort to convert, but it
isn't and I'm honestly trying to lose it to someone else.

>
> Kind regards
>
> robert
>
> --
> remember.guy do |as, often| as.you_can - without end
> http://blog.rubybestpractices.com/
>
>



-- 
Paul Smith
http://www.nomadicfun.co.uk

paul@pollyandpaul.co.uk