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 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 I'm all that
> familiar with the provider sources, either ;) but I noticed a function
> called "prefix_kernel_object_name" in common\utils.cpp which basically
> prefixes "Global\" to all kernel object names in a Terminal Services
> session.
> 
> Now, I would say that for everything *except* embedded, that is 100% the
> correct behaviour. For embedded, however, they should be prefixing
> "Local\"
> to all the object names instead.
> 
> Unfortunately, as far as workarounds go, I'm not sure what you can do. You
> could always just patch the server source yourself and rebuild it, but if
> you're not comfortable doing that, then I don't think there's much that
> can
> be done...
> 
> As for the right place to send your question to, I would probably suggest
> sending it to the [EMAIL PROTECTED] list first (the full
> list
> of mailing lists is here: http://www.firebirdsql.org/index.php?op=lists)
> 
> Dean.



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Reply via email to