From: Ed W <li...@wi...> - 2006-11-03 17:59:20
|
Nathan Leach wrote: > One option I have used is to write an app in Ruby on Rails that > integrates with SL. With Rails ActiveRecord you just give the name of > the table representing your object and you can then address fields as > attributes. Ruby has built-in libraries for dealing with CSV, so > getting data in from there is no problem. > > This is most effective for what I call "master" data (parts, customers, > etc.), but be careful of the ID sequences that SL uses. I had trouble > with those until I found out how to specify them within ActiveRecord. > > I won't bore the entire list with more details, but if you are > interested contact me off list. > > Hi Nathan I'm getting into Rails right now and building some small apps for our business. I am actually working on a web facing frontend for SQLledger so that people can pay their bills directly. I would be curious to see what kind of things you have done with rails because you are obviously diving directly into the data rather than going via the http interface? I haven't really plugged through the tables - is there a quickstart guide that you can offer? I have to say that SQL-Ledger is rather a pain in the arse - it's a nice looking product, but there is minimal support and fairly slow development. The code is quite messy as well. (Having bought the manual I wrote to Dieter to request a feature and he sent me an estimate of $16,000 to implement it... Outside of my budget and not what I would call supportive - he keeps blocking my emails to the list it seems and I sent him at least one patch and didn't even get a reply that it was received...) I would love to have the time to write an alternative in Ruby - I think a rip off would be possible in just a few months, the trick is having a few months free to write it... Regards Ed Wildgoose |