MackMan
Registered User.
- Local time
- Today, 15:43
- Joined
- Nov 25, 2014
- Messages
- 174
As I understand, custom sound VBA codes are different from 32 and 64Bit OS's of Access.
We do an incredible amount of Excel work, so opted for 64 bit Office 2013 which is paying off remarkably compared to 32 bit. Sadly, I would have opted for 32bit Access, but this isn't possible to run side by side.
In doing so, and starting to make the most of Access, I was tinkering with custom sounds in forms.
Notwithstanding, the question would be.. why is this different?
I use the following Declaration on a "PlaySound" module...
When running msgbox appears...
Compile Error
The code in this project must be updated for use on 64-Bit systems.
Please review and update Declare Statements and then mark them with the PtrSafe Attribute.
Am I right in thinking the "Function" part of the declaration, gets changed to PtrSafe? I tried it, and where a sound normally plays, I just hear the standard beep.
Many thanks as always.
We do an incredible amount of Excel work, so opted for 64 bit Office 2013 which is paying off remarkably compared to 32 bit. Sadly, I would have opted for 32bit Access, but this isn't possible to run side by side.
In doing so, and starting to make the most of Access, I was tinkering with custom sounds in forms.
Notwithstanding, the question would be.. why is this different?
I use the following Declaration on a "PlaySound" module...
Code:
Declare Function apisndPlaySound Lib "winmm" Alis "sndPlaySoundA" (ByVal filename As String, ByVal snd async As Long)Compile Error
The code in this project must be updated for use on 64-Bit systems.
Please review and update Declare Statements and then mark them with the PtrSafe Attribute.
Am I right in thinking the "Function" part of the declaration, gets changed to PtrSafe? I tried it, and where a sound normally plays, I just hear the standard beep.
Many thanks as always.
