> > > In previous releases, setting "DatabaseName" with a full
> > connect-string
> > > also set the server and protocol. I was debugging my application and
> > > it kept my protocol to "cpLocal" when using the following
> > connect string:
> > >
> > > martijn-ws/3055:e:\data\helis.fdb
> > >
> > >
> > > During runtime, it was able to access the database, for some reason,
> > > but not when debugging.
> > >
> > >
> > > Got a clue?
> >
> > I found more --
> >
> > I'm now using the .Database property, as I recalled that was
> > the way to go.
> >
> > Protocol is set to TCP/IP (in Params) by the SetDatabase
> > property setter.
> >
> > Next, if I ask for the protocol, I'm getting cpLocal back.
> > Params holds
> > PROTOCOL=TCP/IP though.
> >
> > Is this the debugger messing up on me??
>
> It is likely the parsing for the Database string that is faulty.

No, this seems to be OK.

> You can set the properties Server, Path and Protocol individually if you
> want to stay away from this problem. In the meantime, I'll add this email
> to my folder of potential issues needing a fix.

I'm not sure what's going on -> during a normal run, it works just fine,
during
debugging it messes things up by returning cpLocal instead of cpTCPIP.

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com