Hurrah!

I'm not quite sure why is started working as I've not spent much time on
it today.

Suffice to say we can now make ADO DB connections from .Net projects to
P.SQL V8.5 running on Netware.

At the moment we are using the 'Classic' (ie no!) security model for
backwards compatability with our existing apps.

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Guy Dawson wrote:

And now it's broken again! Back to getting error -4828 from the MS .NET
IDE!

We don't think we changed anything on the server so this is a bit of
a worry!

Anyone else using V8.5 on a Netware server (5.1 SP6 in our case) and
trying to bet ADO DB connections to work?

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Guy Dawson wrote:
It looks like I'm alone in this mission!

We're working again. Going from a system that did not work but has
Classic security setup I did the following:

Turn database security on and assign a password to Master.
Turn database security off again using the assigned password.

OLE DB access now works with the classic security model.

Very odd.

I now need to see if I can find out why the original set-up broke.

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

I can now break and fix this at will!

I have a database called appdb in the PCC under

SERVER
Databases
appdb

and

SERVER
Configuration
Maintain named database
appdb

In SERVER->Databases->appdb->Properties the database is configured to
have security disabled. This means that users cannot be created or
maintained. So far so good.

In SERVER->Configuration->Maintain named database->appdb the database
can configured for Classic, Mixed or Database security.

To keep compatability with existing DOS/Btrieve apps which we're not
going to re-code to do database logons, we obviously need to select the
classic security model. When we do this our userid/password free ADO DB
connections fail!

Playing around, I've found that if I select Database then not only do
our existing DOS/btrieve programs work but that our userid/password free
ADO DB connections no longer fail.

Conversly, if I reselect classic then our existing DOS/btrieve programs
still work but the userid/password free ADO DB connections fail.

This is the reverse of what I've been expecting from the documentation.

A bug somewhere in the ADO DB system I think.

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Guy,

It sounds like you should open a Support Incident, which of course won't
be chargeable if (when?) this is found to be a bug.

Regards,

Jon Grieve
Southdown House Software Ltd.

The U.K's #1 Distributor for Pervasive Software

http://southdown.co.uk
T: (01306) 877998 F: (01306) 887755






Guy Dawson wrote:

Jon Grieve wrote:

I've done that this morning...

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk