On Jun 9, 2011, at 11:16 AM, Jeremy Evans wrote: > On Jun 8, 8:04 pm, Zhi-Qiang Lei <[email protected]> wrote: >> On Jun 9, 2011, at 12:06 AM, Jeremy Evans wrote: >>> As far as I know, there isn't a solution to the issue, it's a >>> limitation in WIN32OLE. If you can find a way to fix it, by all means >>> submit an issue, but unless you can suggest a fix, I'd just close the >>> issue since I don't think it is a problem in Sequel itself. Can't you >>> just use the workaround I gave you? It should work fine with Access >>> unless you have multiple processes modifying the Access database >>> simultaneously. >> >>> Jeremy >> >> Sorry, I don't get your mind. What's the workaround? Do you mean using ADO >> MSSQL adapter instead? > > I posted the workaround code in a previous email: > http://groups.google.com/group/sequel-talk/msg/0c4d8b6563e06ed0 > > Jeremy >
Thank you. I'll try that. Best regards, Zhi-Qiang Lei [email protected] -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
