@IvenBach FWIW, from what I've talked with those outside the murica, they find it easier to read English -- far too much documentation and the third party sources (e.g. SO, forums, blogs, etc.) are in English, so it would be impossible to not read English in programming.
ok, excel guys - i just want to double check I'm not missing something very simple. I need to help control the data input on a worksheet for a bunch of people who want to use Excel as a data entry form because #reasons.
Am I correct in understanding that the Excel table has no way to provide default value?
if they're using an Access backend, they'll have the database in the network folder or whatever, and distribute another Access file containing the forms/reports/code for users to use.
(or in our cases, usually just Access files w/ forms/reports/code that connects to a SQL Server database)
Is there any particular reason why the RenameRefactoring works off the active selection when it is called with a target declaration that does not have a selection?
Public Sub test()
Dim foo As Class1
Dim bar As Class1
Set bar = New Class1
SetItup foo, bar
Debug.Print foo Is Nothing
Debug.Print foo Is bar
End Sub
Private Sub SetItup(ByVal LHS As Class1, ByVal RHS As Class1)
Set LHS = RHS
End Sub
yeah, ByRef failed and I still get Nothing, so I tried ByVal next, and that did not work. Then I made the bad MVCE above but that shows that ByRef does work
I was refactoring the code to be more dry and wrote the sub to do the setup code for a bunch of controls
original code looks like this:
Private Sub ConfigureButton(SourceButton As Access.CommandButton, ViewportTargetButton As Access.CommandButton)
'Required to allow releasing of the button during its click event
If Not SourceButton Is Nothing Then
Set SourceButton = Nothing
End If
Set SourceButton = ViewportTargetButton
Const Evented As String = "[Event Procedure]"
SourceButton.OnClick = Evented
End Sub
and one of the calling code is: ConfigureButton NextButton, This.Viewport.NextButton
the sub will run without errors but once it returns the NextButton is still Nothing, even though the SourceButton was assigned at the end of the sub.
Anyway, the case is that if you've clicked on the next button, the click event of the next button will be the root of the VBA call stack. Trying to assign the button variable to a different button, you get an error. Setting it to Nothing avoids that problem.
The problem is that unless you have some form of IPC, there is no way for the caller to know if the server disconnects. And if there was, well, you wouldn't need either COM or RPC mechanisms.
the simple scenerio would be to open solidworks (or excel), get the com object, close the application manually, so that object in the application is technically not valid i want to be able to determine without trying to catch exceptions...
> Important This function is obsolete and should not be used. Despite its name, it does not guarantee that the pointer is valid or that the memory pointed to is safe to use. For more information, see Remarks on this page.
"This function is typically used when working with pointers returned from third-party libraries, where you cannot determine the memory management behavior in the third-party DLL."
@this fwiw, even in England, there's a dilema... Do I code in English (Colour), or Muricanish (Color)? The former grinds my gears less, until I have to interact with the framework and my #words don't gel with Microsoft's #words. FML.
Back in Tunisia I was taught British English growing up but eventually switched to American English (just because of Silicon Valley). American English is easier to write but way harder to speak and the opposite is true for British English.
Reminds me of a kid I knew. His parents are Chinese and English is his second language. He lived in Australia a couple years and when he came back he had a thick Aussie English accent. He couldn't understand why everyone thought it funny his accent had changed so much.
@Comintern yeah, but... IMO it's done surreptitiously. "Can we have that as a grid?", "Sure". "Can we have column header filters?", "Sure". "Can we have copy and paste?", "Sure". "Can we have a drag handle on the cells?", "Oh... FFS!"