Dean,
I appreciate your comments. No one else seems to be interested. I'll take a
look at the sources. The simplest workaround is to add users to a group with
the appropriate rights. I mostly wanted to pass along what I discovered and
spark a conversation about what should be done.
> > I agree w
> I agree with that assessment. I'm just not sure which mailing list will
> get the most traction. Also, I'm still not sure that I'm not doing
> something wrong with the way I'm using the .Net provider to connect to the
> embedded database.
I'm not very familiar with the server's sources (not that
> > Which explained that for the file mapping to work when connecting to a
> > database on the terminal server, I need to give my users "Create global
> > objects" rights.
>
> It's hard to say, actually. Higher up on the page (in the lpName parameter
> description) it says:
>
> Terminal Servi
This is really crazy. In first mail, you said, that you're not using
connection pooling and now you find that something like connection pool
is and it's enabled. :D
yes, really it is. I *was* not using pooling. just oblivion :-(
On 4/10/07, Jiri Cincura <[EMAIL PROTECTED]> wrote:
manish sh
Hello:
> > I've just repeated tests with demo program using latest 2.1.0 sources
> on .Net 2.0.50727. Errors occured as before.
Ok, i have tested it a little this weekend, without problems, will
continue the tests as soon as possible ( i have pending commits
for 2.1.0 that i will do today )
--
manish shukla wrote:
> Thanks Dan, it worked. Pooling is enabled by default.
This is really crazy. In first mail, you said, that you're not using
connection pooling and now you find that something like connection pool
is and it's enabled. :D
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ |
Hello Carlos,
> It's fine if i test this using latest 2.1.0 sources and .net 2.0 ??
I've just repeated tests with demo program using latest 2.1.0 sources
on .Net 2.0.50727. Errors occured as before.
Regards,
Ralf
-
Take S
