Private Declare Function 64

👉🏻👉🏻👉🏻 ALL INFORMATION CLICK HERE 👈🏻👈🏻👈🏻

Sign up or log in to view your list.
So I had to go in and add in PtrSafe before function calls since I am now using 64bit Excel. So far doing the PtrSafe changes has worked fine except for my mod_Ping. I had to do a #If Win64 Then … #else … #end if statements to make this code work in my macros because it would not work in this part if I had just added in the PtrSafe before each function call.
As you can see I had to also change the longs to LongPtr as well.
When I open up this work book it gives me error only comments may appear after end sub end function or end property. The strange thing is, if i just ignore this and close out the debugger the workbook works fine.
I mean the #End if should be there to end the initial #If calling so I don't know why I would get a compile error for it. Is there something I am not seeing?
Proximus Seraphim Dimitri Davi
Proximus Seraphim Dimitri Davi 464●66 silver badges●2020 bronze badges
Pᴇʜ
48.3k●99 gold badges●4242 silver badges●6464 bronze badges
The declaration is just wrong. DWORD in the MSDN documentation is Long in VBA, not LongPtr. The ip-address is Long as well. – Hans Passant May 30 '18 at 13:08
@HansPassant i went and changed that, it still doesn't resolve the issue of why i am getting a compile error – Proximus Seraphim Dimitri Davi May 30 '18 at 13:31
Do focus on the line number that produces the compile error. Notable is that the #End If is placed incorrectly, if Win64 is defined then the compiler will see two End Function statements. It needs to go after it. – Hans Passant May 30 '18 at 13:37
@HansPassant Hey hans thanks for the reply, i actually tried that before, but what happens is that if i close the work book and re-open the entire thing crashes and i have to re-open the workbook by disabling macros... By defining Win64, do you mean declaring it before i use the way i would dim an object? – Proximus Seraphim Dimitri Davi May 30 '18 at 13:58
I think all Declare statements have to come before any user defined Sub/Function. Try one #If Win64 Then … Else … for the declares first and another afterwards for the user defined Ping function – Pᴇʜ May 30 '18 at 16:25
I think our problem here is that 32bit Excel changes data type Integer to Long data type.
Try replacing Integer with LongPtr.
Giulio Caccin
2,581●66 gold badges●3030 silver badges●4747 bronze badges
Click here to upload your image (max 2 MiB)
You can also provide a link from the web.
By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy
2021 Stack Exchange, Inc. user contributions under cc by-sa
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Accept all cookies Customize settings

Used at the module level to declare references to external procedures in a dynamic-link library (DLL).
Declare statements with the PtrSafe keyword is the recommended syntax. Declare statements that include PtrSafe work correctly in the VBA version 7 development environment on both 32-bit and 64-bit platforms only after all data types in the Declare statement (parameters and return values) that need to store 64-bit quantities are updated to use LongLong for 64-bit integrals or LongPtr for pointers and handles. To ensure backwards compatibility with VBA version 6 and earlier, use the following construct:
[ Public | Private ] Declare Sub name Lib "libname" [ Alias "aliasname" ] [ ( [ arglist ] ) ]
[ Public | Private ] Declare Function name Lib "libname" [ Alias "aliasname" ] [ ( [ arglist ] ) ] [ As type ]
For code to run in 64-bit versions of Microsoft Office, all Declare statements must include the PtrSafe keyword, and all data types in the Declare statement (parameters and return values) that need to store 64-bit quantities must be updated to use LongLong for 64-bit integrals or LongPtr for pointers and handles.
[ Public | Private ] Declare PtrSafe Sub name Lib "libname" [ Alias "aliasname" ] [ ( [ arglist ] ) ]
[ Public | Private ] Declare PtrSafe Function name Lib "libname" [ Alias "aliasname" ] [ ( [ arglist ] ) ] [ As type ]
Optional. Used to declare procedures that are available to all other procedures in all modules.
Optional. Used to declare procedures that are available only within the module where the declaration is made.
Required on 64-bit. The PtrSafe keyword asserts that a Declare statement is safe to run in 64-bit versions of Microsoft Office.
Optional (either Sub or Function must appear). Indicates that the procedure doesn't return a value.
Optional (either Sub or Function must appear). Indicates that the procedure returns a value that can be used in an expression.
Required. Any valid procedure name. Note that DLL entry points are case-sensitive.
Required. Indicates that a DLL or code resource contains the procedure being declared. The Lib clause is required for all declarations.
Required. Name of the DLL or code resource that contains the declared procedure.
Optional. Indicates that the procedure being called has another name in the DLL. This is useful when the external procedure name is the same as a keyword. You can also use Alias when a DLL procedure has the same name as a public variable, constant, or any other procedure in the same scope. Alias is also useful if any characters in the DLL procedure name aren't allowed by the DLL naming convention.
Optional. Name of the procedure in the DLL or code resource. If the first character is not a number sign (#), aliasname is the name of the procedure's entry point in the DLL. If (#) is the first character, all characters that follow must indicate the ordinal number of the procedure's entry point.
Optional. List of variables representing arguments that are passed to the procedure when it is called.
Optional. Data type of the value returned by a Function procedure; may be Byte, Boolean, Integer, Long, LongLong, LongPtr, Currency, Single, Double, Decimal (not currently supported), Date, String (variable length only), Variant, a user-defined type, or an object type. (LongLong is a valid declared type only on 64-bit platforms.)
The arglist argument has the following syntax and parts:
[ Optional ] [ ByVal | ByRef ] [ ParamArray ] varname [ ( ) ] [ As type ]
Optional. Indicates that an argument is not required. If used, all subsequent arguments in arglist must also be optional and declared by using the Optional keyword. Optional can't be used for any argument if ParamArray is used.
Optional. Indicates that the argument is passed by value.
Indicates that the argument is passed by reference. ByRef is the default in Visual Basic.
Optional. Used only as the last argument in arglist to indicate that the final argument is an Optional array of Variant elements. The ParamArray keyword allows you to provide an arbitrary number of arguments. The ParamArray keyword can't be used with ByVal, ByRef, or Optional.
Required. Name of the variable representing the argument being passed to the procedure; follows standard variable naming conventions.
Required for array variables. Indicates that varname is an array.
Optional. Data type of the argument passed to the procedure; may be Byte, Boolean, Integer, Long, LongLong, LongPtr, Currency, Single, Double, Decimal (not currently supported), Date, String (variable length only), Object, Variant, a user-defined type, or an object type. (LongLong is a valid declared type only on 64-bit platforms.)
If you include an argument list, the number and type of arguments are checked each time the procedure is called. The following example takes one Long argument:
This example shows how the Declare statement is used at the module level of a standard module to declare a reference to an external procedure in a dynamic-link library (DLL). You can place the Declare statements in class modules if the Declare statements are Private.
Have questions or feedback about Office VBA or this documentation? Please see Office VBA support and feedback for guidance about the ways you can receive support and provide feedback.
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Glossary of terms for Visual Basic Editor (VBE).
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

Porno Chubby Naked Cleaning Company
Mainstream Erotic Adult Film
Lesbian Videos 69
Children's Sex Video
Bachelorette Party Turns Lesbian
Declare statement (VBA) | Microsoft Docs
32 Bit And 64 Bit Api Declarations For Vba Developers ...
Excel: Declaring API functions in 64 bit Office
Declaring API functions in 32 or 64 bits
Windows API declarations in VBA for 64-bit - Codekabinett
Copy & Paste In Access 64-Bit - Microsoft Community
64 Bit Win API Call - SHGetPathFromDList - Autodesk Com…
Aggiornamento codice per utilizzo in sistemi a 64 bit ...
Code difference in 64 bit and 32 bit
Private Declare Function 64