Another consideration is that the db library doesn't support Microsoft
SQL Server directly. It may work fine via ODBC (I don't know
first-hand because I haven't used SQL Service since `db' was added to
Racket).
In a previous life I did use FreeTDS with Racket on Linux to talk to a
SQL Server. A duct tape approach, but it can work fine for certain
purposes. After all it is essentially how SQL Studio is talking to SQL
Server on the wire, beneath all the layers of GUI and IntelliSensing.
;)
Also in a previous life, on the Excel side: I've used Racket's COM FFI
to talk to a local install of Excel and build a workbook. But these
days it's probably simplest to make a file for Excel to load -- CSV if
only the data matters, or XML if you need to specify cell formatting
or other Excel features.
On Thu, Oct 11, 2012 at 12:53 PM, Galler <lzgal...@optonline.net> wrote:
> Greg Graham <GGraham@...> writes:
>
>>>do you think this is a crazy idea or not?
>
> I won't call it crazy.
>
> Can I call it overengineered?
>
> I would write the following in T-SQL to achieve what you want:
>
> sp_configure 'Ad Hoc Distributed Queries', 1
> reconfigure
>
> USE [your-database]
> GO
>
> insert into OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel
> 8.0;Database=C:\test.xls','select * from [sheet1$]')
> SELECT CODE FROM dbo.[your table name]
>
>
>
> ____________________
> Racket Users list:
> http://lists.racket-lang.org/users
____________________
Racket Users list:
http://lists.racket-lang.org/users
