NDAP & Vista
Michael Holmes
Thanks.
Guenter
there is no longer any active engineering on any of the OCXs. There are no
plans to modify, fix or enhance the activex controls.
They were moved to the unsupported list some time back so it's use at your
own risk.
greets, Günter.
"Michael Holmes" <Holm...@scc-fl.edu> wrote in
news:45ED602E.F...@scc-fl.edu:
> --____RFPFADQMPXISDEHOBURG____
>
> --____LQCQPPHJFNAFFILZTTFZ____
> <HTML><HEAD>
> <META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
> <META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
> <BODY style="MARGIN: 4px 4px 1px; FONT: 10pt MS Sans Serif; COLOR:
> #000000">Is there going to be a VISTA release of the NDAP OCX's?
> We've/I've been mandated to have VISTA up and running in our classrooms
> by our Fall term in August.... come hell or high water. I need to
> re-write a few of my utilities before then and they rely on NDAP
> controls.<BR><BR>Thanks.<BR></BODY></HTML>
> --____LQCQPPHJFNAFFILZTTFZ____--
Michael Holmes
I have a whole set of applications that I wrote in VB using OCX to access
eDir... I heavily rely on these applications. Now that we're moving to VISTA
none of those will work.
Is there any substitute method(s) for using OCX to access eDir via VB?
Wow again.... Now I am more disappointed in Novell than ever. If Novell
keeps this up AD begins to sound more attractive.
Thanks.
>>> Guenter<devf...@novell.com> 3/6/2007 7:40 PM >>>
Michael Holmes
>>> Guenter<devf...@novell.com> 3/7/2007 10:57 AM >>>
Hi Michael,
> Wow.... I guess I'm REALLY up a creek without a paddle.
>
> I have a whole set of applications that I wrote in VB using OCX to
> access eDir... I heavily rely on these applications. Now that we're
> moving to VISTA none of those will work.
compatiblity? What causes that these controls do no longer work?
> Is there any substitute method(s) for using OCX to access eDir via VB?
Anyway, with LDAP you're also one step closer to AD, smile....
> Wow again.... Now I am more disappointed in Novell than ever. If Novell
> keeps this up AD begins to sound more attractive.
leave - or did you think these were all only lazy bones? Hey, they fired the
developers, not the managers.....
But you should probably directly send a mail to sup...@novell.com and ask
what benefits the new marriage with M$ has now for us all.... - perhaps you
can run SuSE natively and then Vista inside Xen, and another virtual Xen with
W2K for backwards compatiblity...?
greets, Guenter.
Guenter
"Michael Holmes" <Holm...@scc-fl.edu> wrote in
news:45EE7881.F...@scc-fl.edu:
> Wow.... I guess I'm REALLY up a creek without a paddle.
>
> I have a whole set of applications that I wrote in VB using OCX to
> access eDir... I heavily rely on these applications. Now that we're
> moving to VISTA none of those will work.
why? Sorry, but I've not used Vista yet - but is there no downward
compatiblity? What causes that these controls do no longer work?
> Is there any substitute method(s) for using OCX to access eDir via VB?
probably you can do most things with LDAP, but certainly not everything.
Anyway, with LDAP you're also one step closer to AD, smile....
> Wow again.... Now I am more disappointed in Novell than ever. If Novell
> keeps this up AD begins to sound more attractive.
Guenter
"Michael Holmes" <Holm...@scc-fl.edu> wrote in
news:45EE9FAB.F...@scc-fl.edu:
> I can not get the ActiveX controls, NWDIR.OCX for example, to register
> in Vista. We are using the 32bit version. Our mandate is due to the fact
> that "we" are teaching these products so we are ALWAYS on the bleeding
> edge. I don't have much more blood to give.
Can you tell us what is really needed? I mean you have probably own OCX
written already - is it sufficient to re-compile them with the recent MSVB
version? Or is it more work? Does it probably make sense to ask for making
the sources open?
Also the developers clearly expressed their concerns to the decision
makers...
greets, Guenter.
Michael Holmes
I use Novell's NWDIR.OCX in particular to create, update and otherwise
manipulate eDir user objects. My main concern is a program I wrote to simply
enable a user's login. (the student runs the program, agrees to stated lab
rules and then the program "unlocks"/enables their account. I have over 38K
student objects in our tree). The code that uses NWDIR.OCX is only 5 lines
long but they are an important 5 lines. My VB program seems to run under
Vista but the OCX will not register which means in essence my program won't
run.... properly.... thus my concern.
My code snippet looks like:
Set Entry = NWDir1.FindEntry(StartingContext & Right$(StudentEmplID, 1)
& "\" & StudentLoginID)
result = Entry.SetFieldValue("login disabled", Null)
If result = True Then
Entry.Update
UnlockID = True
Else
MsgBox "A problem has occured in unlocking your ID. Please let a lab
assistant or Instructor know.", vbCritical, "ERROR Unlocking ID"
End If
---------------
Seems very simple but it's very important to me.....
Thanks for listening.
"Guenter" <devf...@novell.com> wrote in message
news:eXBHh.692$1q5...@prv-forum2.provo.novell.com...
Guenter
"Michael Holmes" <holmesm_@@scc-fl.edu> wrote in
news:CxLHh.1228$1q5...@prv-forum2.provo.novell.com:
> My own OCX? Not quite. I'm not that accomplished.
> I use Novell's NWDIR.OCX in particular to create, update and otherwise
> manipulate eDir user objects. My main concern is a program I wrote to
> simply enable a user's login. (the student runs the program, agrees to
> stated lab rules and then the program "unlocks"/enables their account. I
> have over 38K student objects in our tree). The code that uses NWDIR.OCX
> is only 5 lines long but they are an important 5 lines. My VB program
> seems to run under Vista but the OCX will not register which means in
> essence my program won't run.... properly.... thus my concern.
hmm, Du you have already a Client32 for Vista then? I guess thats required in
order to get the OCX working, or? I currently cant find one:
http://www.novell.com/beta/auth/beta.jsp?id=2046&type=1
and seems even beta starts this month...
Then when looking at your code snippet I'm confident that we might find another
working solution which can replace the OCX; f.e. direct calls into Client32
DLLs might be a first choice (provided that we have a Vista Client), or the
move to LDAP as second....
beside that I'm still asking me why the OCX doesnt register on Vista; probably
we should first try to find out what's the real reason; it might be a missing
DLL with the Vista CLient32 or something like that, or probably a DlL from the
OS which was renamed now....
Do you know of the Dependecy Walker from VS? I'm not sure since I've never used
for such things, but it might be possible that you can track down what external
DLLs the OCX depends on, and then perhaps copy over the missing bits...
http://www.dependencywalker.com/
greets, Guenter.
Michael Holmes
"technology concept?" version of the Novell Client for VISTA. As you said
perhaps that's the problem... Never really thought of that. I will get the
dependacy program and give it a try too.
Thanks.
"Guenter" <devf...@novell.com> wrote in message
news:toWHh.1551$1q5....@prv-forum2.provo.novell.com...
Mark Clark
to .NET, we ditched the OCX controls and instead now use "clsNovellAPI"
by Karl Durrance.
The VB6 version is here: http://developer.novell.com/wiki/index.php/VB6
_Class_Module_Using_Novell_C_Libraries
The .NET version is here: http://developer.novell.com/wiki/index.php?
title=VB.NET_Class_Module_Using_Novell_C_Libraries&redirect=no
There are also newsgroups on the APIs on this news server. The
newsgroups are:
novell.forge.vb6-api-class.devforumclsnovellapi
novell.forge.vbnet-api-class.clsnovellapinetdevforum
The conversion from OCX controls to this API library was pretty
painless. We didn't use the OCX controls to their fullest, but what we
were doing with the OCX controls we could do with the API. When I
needed a new function that I had with an OCX but which was not in the
API, I added it. Basically, I added two functions that dealt with
Volumes. I submitted my changes to Mr. Durrance. You might check out
the API and see if it would help you. You might also check with Mr.
Durrance to see if he is planning on releasing a new version anytime
soon with any new changes.
HTH
In article <45ED602E.F...@scc-fl.edu>, Holm...@scc-fl.edu
says...
Mark Clark
this will work with either Linux or NetWare kernels. It -does- require
the Novell Client. I think that since it is using the Client32 APIs to
function that it does not care what kernel is "behind the curtain".
In article <y%vJh.303$W_4...@prv-forum2.provo.novell.com>,
frank....@detwentsezorgcentra.nl says...
> Hello Mark.
> Will this clsNovellAPI work with OES on linux or only on netware kernel?
> Also, is the Novell Client still needed?
>
> Cheers,
> Frank
frankpeters
Will this clsNovellAPI work with OES on linux or only on netware kernel?
Also, is the Novell Client still needed?
Cheers,
Frank