Screen updating translate

Since the 64 bit declarations also work on 32 bit Office 2010, all you have to test for is VBA7: Have a function declaration which is not on this list? Re: client uses Citrix to distribut my MS Access application that uses Windows API declare statements. And most users are probably running from Windows 7.

I invite you to send me your (working and tested!!! I also welcome comments and suggestions on improvements! Can you please exapand on a situation for migrating to Windows Server 2008 R2 and the 32 Bit of Office 2010?

How to determine what is a memory address and what is data? My IT colleague told me that owc11 is 32bit version only. Thanks, Martin Hi Martin, Unfortunately, you cannot use 32 bit controls in 64 bit Office and the Office Web controls are strictly 32 bit.

You just have to read the MSDN documentation for the API functions (the C version) and it will tell you. Can do I sonething with this or replace owc11 with some other file? So you will have to revert to a different method entirely.

The Send Message API is a good example because it uses both types: 32-bit: The first argument -h Wnd- is a window handle, which is an address in memory. NB: what isn't mentioned is that the executable unzips the information to this folder on your hard drive: C:\Office 2010 Developer Resources\Documents\Office2010Win32API_Ptr Safe I disagree with WPARAM (such as in Send Message) as it is defined as a UINT_PTR which is defined as 64 bit pointer on 64 bit platforms and a 32 bit pointer on 32 bit platforms per MSDN and windef.h: typedef UINT_PTR WPARAM; #if defined(_WIN64) typedef unsigned __int64 UINT_PTR; #else typedef unsigned int UINT_PTR; #endif Hi, I've got MS Excel 2003 file with VBA macros, but I already have MS 2010 with 64bit rate.

But to get declarations to work correct across the three platforms, I believe I need to use the win64 constant, as per the MS 2010 Help file: ' Conditional Compilation Example #If Vba7 Then ' Code is running in the VBA7 editor.

This is because a 64-bit OS has a memory space that is too large to hold in a Long data type variable. So in 64 bits it takes, at least, AN HOUR while in 32 bits it takes 15 SECONDS!!! I think is a bug of Office 2010 64bits, and i'm thinking about install 32 bits to get that problems off. Global constant declarations for the constants that the provided Declare statements use.

Arguments or return values that represent data will still be declared Long even in 64-bit. Type declarations for the user-defined types (structures) that the provided Declare statements use. Family ID=035b72a5-eef9-4baf-8dbc-63fbd2dd982b&displaylang=en Hi Ulrik, Thanks for the link!

Microsoft has provided an updated version of the Win32with all proper declarations available for download here: Office 2010 Help Files: Win32API_Ptr Safe with 64-bit Support When you run the installer after downloading the file form the link above, it does not tell you where it installed the information. I cant get these Api declarations to work with a 64bit office version. thanks in advance Tomas Option Explicit #If VBA7 Then Private Declare Ptr Safe Function Find Window Lib "user32" Alias "Find Window A" _ (By Val lp Class Name As String, By Val lp Window Name As String) As Long Ptr Private Declare Ptr Safe Function Find Window Ex Lib "user32" Alias "Find Window Ex A" _ (By Val h Wnd1 As Long Ptr, By Val h Wnd2 As Long Ptr, By Val lpsz1 As String, By Val lpsz2 As String) As Int Ptr Private Declare Ptr Safe Function Send Message Lib "user32" Alias "Send Message A" _ (By Val hwnd As Long Ptr, By Val w Msg As Long, By Val w Param As Long Ptr, By Val l Param As Any) As Long Ptr #Else Private Declare Function Find Window Lib "user32" Alias "Find Window A" _ (By Val lp Class Name As String, By Val lp Window Name As String) As Long Private Declare Function Find Window Ex Lib "user32" Alias "Find Window Ex A" _ (By Val h Wnd1 As Long, By Val h Wnd2 As Long, By Val lpsz1 As String, By Val lpsz2 As String) As Long Private Declare Function Send Message Lib "user32" Alias "Send Message A" _ (By Val hwnd As Long, By Val w Msg As Long, By Val w Param As Integer, By Val l Param As Any) As Long #End If Hi, Can you help me, to place Long Ptr insted of Long in delarations. Because here I can't post more then 2000 chars in one post Public Declare Ptr Safe Function WSAStartup Lib "wsock32.dll" (By Val w Version Required&, lp WSADATA As WSADATA) As Long Public Declare Ptr Safe Function WSACleanup Lib "wsock32.dll" () As Long Public Declare Ptr Safe Function gethostbyname Lib "wsock32.dll" (By Val host_name As String) As Long Public Declare Ptr Safe Function gethostname Lib "wsock32.dll" (By Val host_name As String, By Val namelen As Integer) As Integer Public Declare Ptr Safe Function setsockopt Lib "wsock32.dll" (By Val S As Long, By Val level As Long, By Val optname As Long, optval As Any, By Val optlen As Long) As Long Public Declare Ptr Safe Function w_socket Lib "wsock32.dll" Alias "socket" (By Val lng Af As Long, By Val lng Type As Long, By Val lng Protocol As Long) As Long Public Declare Ptr Safe Function w_closesocket Lib "wsock32.dll" Alias "closesocket" (By Val socket Handle As Long) As Long Public Declare Ptr Safe Function w_bind Lib "wsock32.dll" Alias "bind" (By Val SOCKET As Long, Name As SOCKADDR_IN, By Val namelen As Long) As Long Public Declare Ptr Safe Function w_connect Lib "wsock32.dll" Alias "connect" (By Val SOCKET As Long, Name As SOCKADDR_IN, By Val namelen As Long) As Long Public Declare Ptr Safe Function w_send Lib "wsock32.dll" Alias "send" (By Val SOCKET As Long, buf As Any, By Val length As Long, By Val Flags As Long) As Long Public Declare Ptr Safe Function w_send To Lib "wsock32.dll" Alias "sendto" (By Val SOCKET As Long, buf As Any, By Val length As Long, By Val Flags As Long, remote Addr As SOCKADDR_IN, By Val remote Addr Size As Long) As Long Public Declare Ptr Safe Function w_recv Lib "wsock32.dll" Alias "recv" (By Val SOCKET As Long, buf As Any, By Val length As Long, By Val Flags As Long) As Long Hi Satyendra, I'm sorry I can't help you with that on short notice, I'm way too busy to do this for you. I tried to find those functions in your given MSDN site. Can you help me sort this issue or suggest some good material where I can get all these function syntaxes. --------------------------------------------- #If VBA7 Then Private Type LASTINPUTINFO cb Size As Long Ptr dw Time As Long Ptr End Type Private Declare Ptr Safe Sub Get Last Input Info Lib "USER32" (By Ref plii As LASTINPUTINFO) #Else Private Type LASTINPUTINFO cb Size As Long dw Time As Long End Type 'Jan, The following references are checked: - Visual Basic For Applications - Microsoft Excel 14.0 Object Library - OLE Automation - Microsoft Office 14.0 Object Library I quickly scrolled through the entire reference list and did not see anything marked "Missing".

Look in this -new- folder on your C drive: C:\Office 2010 Developer Resources\Documents\Office2010Win32API_Ptr Safe You can find a list of the old Win32 API declarations here: Visual Basic Win32 API Declarations Microsoft also published a tool to check your code for 64 bit related problems, called the Microsoft Office Code Compatibility inspector addin. Protect ("BCG") Beep End Sub ---------------- Thanks I tried what you said but the result was very little faster. I suggest you to find the information on each of the functions you mention on the Microsoft MSDN site: I mentioned above: Anything called a handle, pointer, brush or any other object type will require a Long Ptr in 64-bit. Satyendra Hi, I modified all the declarations, except the select statement. Public Declare Ptr Safe Function w_select Lib "wsock32.dll" Alias "select" (By Val nfds As Long, read Fds As fd_set, write Fds As fd_set, except Fds As fd_set, timeout As timeval) As Long Satyendra Hello. Hi Maria, Thanks for letting me know, great you could solve your problem.

Search for screen updating translate:

screen updating translate-32screen updating translate-58screen updating translate-39screen updating translate-2

With the introduction of Windows 7 and Office 2010 VBA developers face a new challenge: ensuring their applications work on both 32 bit and 64 bit platforms.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “screen updating translate”

  1. Jane*, a middle-aged woman from Warwickshire, had a lucky escape a few years ago when she very nearly handed over a sizeable sum of money to an online scammer who did in fact claim to be an engineer.