I have created a box using the shapes icon and labeled it "Holds/Complaints" and attach it to a macro for a user form. I need the Holds/Complaints button to be floating in the exact same spot regardless of how much I scroll down or to the right. I have researched multiple threads on how to make this happen and it worked for them but for the life of me, I cannot get that button to float, so frustrating.
This will solve your problem...
https://www.extendoffice.com/documen...nd-button.html
Scroll down and select any cell...
Good Luck...
I don't presume to know what I am doing, however, just like you, I too started somewhere...
One-day, One-problem at a time!!!
If you feel I have helped, please click on the [★ Add Reputation] to left of post window...
Also....Add a comment if you like!!!!
And remember...Mark Thread as Solved...
Excel Forum Rocks!!!
Only problem I have now is that the command button only stays if I am navigating through select the cell so the command button reappears. If I use the scroll bar then the command button does not stay.
The cell part works better but still needs tweaking as to exact positioning the scrolling will require some more tweaking
---
Hans
"IT" Always crosses your path!
May the (vba) code be with you... if it isn't; start debugging!
If you like my answer, Click the * below to say thank-you
I found this code on another form
If you remove the + oCell.Width the button will be on the selected cell
Please Login or Register to view this content.
Perhaps making use of a userform containing command button...
Set ShowModal property to false
Last edited by Sintek; 12-14-2017 at 04:21 AM.
Yes but the OP wants it to move with the selection
As per OP...Might be misinterpreting...I need the Holds/Complaints button to be floating in the exact same spot regardless of how much I scroll down or to the right.
My mistake
Minor modification so it works with 64 and 32 bit
PtrSafe
If it's just a button, why not put it on the Ribbon?
Don
Please remember to mark your thread 'Solved' when appropriate.
Maybe because it won't 'Float'?
It's a good idea, or even the QAT but then you would have to code it so it's available to all who use the file
I presume it only needs to "float" so it remains in view while scrolling, which a Ribbon button would do.
.
Here are several examples that may solve the issue :
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.
Private Declare Function FindWindow Lib "user32" _
Alias "FindWindowA" ( _
ByVal lpClassName As String, _
ByVal lpWindowName As String) As Long
Private Declare Function GetWindowLong Lib "user32" _
Alias "GetWindowLongA" ( _
ByVal hWnd As Long, _
ByVal nIndex As Long) As Long
Private Declare Function SetWindowLong Lib "user32" _
Alias "SetWindowLongA" ( _
ByVal hWnd As Long, _
ByVal nIndex As Long, _
ByVal dwNewLong As Long) As Long
Thanks everyone for your responses in helping me, I appreciate your help. You all have helped me get started of what I'm sure my boss will be impressed.
However, I want to send a Special Thanks to Logit. This person (boy or girl) helped out but beyond that he gave me some additional options of different macros that I didn't even think of, I really like the one where the command button appears 2 cells away from the cell that you have selected, super cool.
How do I get the commandbutton1 to appear on the left side of the cell that I have selected?
in regard to the compile error if you are still having it
find
and replace withPlease Login or Register to view this content.
Please Login or Register to view this content.
If you want something done right... find a forum and ask an online expert.
Time flies like an arrow. Fruit flies like a banana.
Write it like this to make if compatible with both 64 and 32 bit
Please Login or Register to view this content.
It takes more than just adding PtrSafe. For instance all the hWnd should be LongPtr and not Long, several of the functions should return LongPtr- and in fact be changed to call different functions- and corresponding variables in the code will also need to be altered.
I beg to disagree, I've written quite some code and the #IF VBA7 .... #Else .... #End If declaring PtrSafe in the true section nevear cause dany issues and all ar set as Long
The fact is that the #if VBA7 and PtrSafe interpret the As Long as a LongPtr
No it does not. A LongPtr resolves to either a Long or a LongLong depending on the bitness. Using a Long incorrectly may lead to your program terminating abruptly with no warning (at best).
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks