On Tuesday, February 14, 2017 4:05:25 AM EST you wrote:

>
> That is a workaround to use non-ascii database filenames. Jaybird 3
> already does that automatically when connecting to Firebird 2.5 or
> higher. Setting utf8_filename=1 is not necessary with Jaybird 3, and
> this is not related to your problem.

I am simply trying to connect via any means using Jaybird 3. Thus far I have
never been able to connect or use Jaybird 3.

--
William L. Thomson Jr.


[Non-text portions of this message have been removed]