NNOTES.dll

hi all,

i want to read the nnotes.dll file present in my pc but while opeing its not supporting, so its coming up with junk data, can any one pls help by saying in which file(format) it could open.

thnx

Subject: NNOTES.dll

It’s a compiled binary file. What were you hoping to find?

Subject: RE: NNOTES.dll

actually i get some functions which are taken from the NNOTES.dll file, now i want to see the body of those functions as

Declare Private Function NSFDbOpen Lib wAPIModule Alias “NSFDbOpen”( Byval P As String, hDB As Long) As Integer

Declare Private Function NSFDbClose Lib wAPIModule Alias “NSFDbClose”( Byval hDB As Long) As Integer

Declare Private Function NSFNoteUpdate Lib wAPIModule Alias “NSFNoteUpdate”( Byval hNT As Long, Byval F As Integer) As Integer

Declare Private Function NSFNoteCreate Lib wAPIModule Alias “NSFNoteCreate”( Byval hDB As Long, hNT As Long) As Integer

Declare Private Function NSFNoteSetInfo Lib wAPIModule Alias “NSFNoteSetInfo”( Byval hNT As Long, Byval M As Integer, V As Any) As Integer

Declare Private Function NSFNoteSign Lib wAPIModule Alias “NSFNoteSign”( Byval hNT As Long) As Integer

Declare Private Function NSFItemSetTextSummary Lib wAPIModule Alias “NSFItemSetText”( Byval hNT As Long, Byval N As String, Byval T As String, Byval nT As Integer, Byval S As Integer) As Integer

Declare Private Function NSFItemAppend Lib wAPIModule Alias “NSFItemAppend”( Byval hNT As Long, Byval F As Integer, Byval N As String, Byval nN As Integer, Byval T As Integer, Byval V As String, Byval nV As Long) As Integer

Declare Private Function OSPathNetConstruct Lib wAPIModule Alias “OSPathNetConstruct”

( Byval NullPort As Long, Byval Server As String, Byval File As String, Byval PathNet As String) As Integer

Declare Sub NEMDisplayError Lib “NNOTESWS” Alias “NEMDisplayError”( Byval E As Long)

they are all taken from nnotes.dll

Subject: RE: NNOTES.dll

Again, the file is a compiled binary. What you have is the signatures of the API functions. I suppose you could try to use a decompiler to get to a reasonable representation of the source code (the entry points for the functions would be readable, but the rest would be only barely readable since the original variable names and so forth would be replaced by tokens that the decompiler inserts). But that’s NOT how to go about things.

If you want the C API documentation, download the C API documentation. Both the documentation and the user guide are free downloads. But then, someone else already told you that in another posting.