[AccessD] DLL question (was Broadcast a message)

Hi Andy

> To be honest Gustav I don't know if it's what I want or not. I just want to
> send a message across the network, which I thought would be trivial but is
> proving otherwise. I found the DLL on the network and copied it to the
> workstation, but it's not working, and attempts to register it fail too. I'm
> stumped by how difficult this is proving.

Don't be. You are working with a solution which reads the bindery
which was left with NetWare 3.12 and replaced with NDS now eDirectoy.
You can still maintain a bindery but most network admins don't.

Here's another link (look for BrdCast and Broadcast):

http://developer.novell.com/ndk/doc/samplecode/activex_ndap_sample/index.htm

In any case you'll need two ocx'es, nwsrva.ocx and nwdir.ocx, which
are free to download.

/gustav


>> By second thought, this is code for the NetWare Bindery, not the NDS.
>> Are you sure this is what you want?
>>
>> I looked for the dll on my machine and it is not present.
>> If you can locate it, have you tried registering it using regsvr32.exe?
>>
>> /gustav
>>
>>
>> > It's exactly the code from the link you kindly gave me:
>>
>> > http://www.clippings.vivitec.com.au/pp_article_id_8.html
>>
>>
>> > -- Andy Lacey
>> > http://www.minstersystems.co.uk
>>
>>
>> >> -----Original Message-----
>> >> From: accessd-bounces at databaseadvisors.com
>> >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
>> >> Gustav Brock
>> >> Sent: 09 September 2004 17:27
>> >> To: Access Developers discussion and problem solving
>> >> Subject: Re: [AccessD] DLL question (was Broadcast a message)
>> >>
>> >>
>> >> Hi Andy
>> >>
>> >> What does your complete code look like?
>> >>
>> >> /gustav
>> >>
>> >>
>> >> > Am trying to use Novell messaging for broadcasting
>> >> messages, and have
>> >> > code (thanks for pointer Gustav) to use API calls in
>> >> NWNETAPI.DLL. But
>> >> > whenever I run the code I get a "Path not found:
>> >> NWNETAPI.DLL" error.
>> >> > Even if I put the specific location of the DLL I still get
> it. Does
>> >> > this mean it uses other DLL's, and if so how do I find out
>> >> what else I
>> >> > need? Or what else could it be?