pepe wrote in post #966625: [...] > To make the whole picture "even better" the client will not only use > Windows but MSSQL as well, which is how the whole mess started > actually (ODBC problems).
Then do what we're doing here: use a separate *nix server for the Rails app, and connect with TinyTds. That way Rails and MSSQL both get the environment in which they're happiest. If you can't do that, JRuby and jTDS might work, or you could use MRI and ODBC. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
