Luca Bertoncello <[EMAIL PROTECTED]> schrieb: > "Jeff Loucks" <[EMAIL PROTECTED]> schrieb: > > > Like I said, I stripped this down from some more complex code, so you > > may have to play with it a bit. What is probably happening is that > > NetLibIFGet() is returning another kind of error than the two expected. > > Check for netErrUnknownSetting, which means you're done, and > > netErrPrefNotFound, which means the instance hasn't sufficient info. Any > > other error is probably telling you NetLib isn't happy, which means you > > don't have a newtwork. > > So, I made some experiments... > > First: NetLibIFGet returns netErrInterfaceNotFound instead of > netErrInvalidInterface when the interface number is not valid... > Second: NetLibIFSettingGet will ALWAYS return 0 for netIFSettingUp
Some other information... If I call NetLibOpen BEFORE NetLibIFSettingGet I can get the right values (for example the interface names). But if I don't call NetLibOpen I get always trash... So, it seems it is necessary to call NetLibOpen before all other functions, but if I call NetLibOpen, it tries to estabilish a connection... Any idea for a solution? Thanks Luca Bertoncello ([EMAIL PROTECTED]) -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
