when you need to update a table on a MySQL linked server and update openquery ... from... join refuses to work and exec(@sql) at [MYSQL] works perfectly fine and you've wasted enough time on this already, yeah
Am I getting a false positive inspection? I've got this:
Public Sub Foo
Set notifier = New UserNotifier
notifier.formField = Form_GenQuarterlyRpt.ProcessStatus
End Sub
'UserNotifier:
Public Property Get formField() As TextBox
Set formField = this.formField
End Property
Public Property Let formField(ByVal Value As TextBox)
Set this.formField = Value
End Property
and I'm getting Object variable 'formField' is assigned without the 'Set' keyword inspection
if you want to reference a specific form, it's better to do something like Dim f As Form_MyForm : Set f = Forms("MyForm") and then subsequently refer to the f in your code. (there's an issue with the global instance but that is better than the syntax you are using ATM)
'@Folder("Utilities.Tools")
Option Compare Database
Option Explicit
Private Type TInfo
formField As TextBox
End Type
Private this As TInfo
Public Property Get formField() As TextBox
Set formField = this.formField
End Property
Public Property Let formField(ByVal Value As TextBox)
Set this.formField = Value
End Property
Public Sub NotifyTee(ByVal logLevel As logLevel, ByVal messageText As String)
UpdateScreen messageText
UpdateLog logLevel, messageText
End Sub
Private Sub UpdateScreen(ByVal messageText As String)
I'm not talking about the tee/notifier. I'm referring to the usage of the default instance (e.g. directly referencing the Form_GenQuarterlyRpt default instance)
thanks, @this. Brain is turning to mush at the moment, so I'll digest in the morning. Have to go pick up my new HD & start testing it before installing in the file server to replace a dying one...
then it depends on the implementation. It may error or may not.
remember, VBA loves to do all those voodoo implicit conversions, so it will try to convert whatever. If it succeeds, then everything's fine (for some value of "fine"). If not, you get a weird error that makes no sense.
I suppose ADODB then uses the connection string to pull an active connection from the connection pool... which might have interesting consequences given multiple open connections using the same connection string, where only one has an active transaction that you mean to use for the command
Private col As VBA.Collection
Public Property Let Example(RHS As VBA.Collection)
Set col = RHS
End Property
Public Property Set Example(RHS As VBA.Collection)
Set col = RHS
End Property
Public Property Get Example() As VBA.Collection
Set Example = col
End Property
Public Sub Test()
Dim x As Class1
Dim c As VBA.Collection
Set x = New Class1
Set c = New VBA.Collection
x.Example = c
Debug.Print x.Example Is c
Set x.Example = c
Debug.Print x.Example Is c
End Sub
Public Sub Test()
Dim x As Class1
Dim c As VBA.Collection
Set x = New Class1
Set c = New VBA.Collection
x.Example = c
Debug.Print x.Example Is c
Set x.Example = c
Debug.Print x.Example Is c
Let x.Example = c
Debug.Print x.Example Is c
End Sub
The ADODB.Command is able to take a String. Since there is no function overloading, I do not think that it can take the connection directly via the let.
Confirmed.... with a password-login, Let cmd.ActiveConnection = conhas to be using the object, not the default member
because if I take the value of the con.ConnectionString and apply to the cmd.ActiveConnection, it errors saying that the user is not authenticated (no password)
but applying the open con to the cmd.ActiveConnection (whether without any explicit keyword, with Set, or Let) all succeed.
I think it's reasonable to assert that the default member is not involved here.
from what I see, VBA doesn't have that restriction, exactly.
Public Property Let Example(RHS As Variant)
Set col = RHS
End Property
Public Property Set Example(RHS As VBA.Collection)
Set col = RHS
End Property
Public Property Get Example() As Variant
Set Example = col
End Property
so is this:
Public Property Let Example(RHS As VBA.Collection)
Set col = RHS
End Property
Public Property Set Example(RHS As Variant)
Set col = RHS
End Property
Public Property Get Example() As VBA.Collection
Set Example = col
End Property
but not all permutations are legal, though.
this gives a compile error:
Public Property Let Example(RHS As VBA.Collection)
Set col = RHS
End Property
Public Property Set Example(RHS As Variant)
Set col = RHS
End Property
Public Property Get Example() As Variant
Set Example = col
End Property
Wonder if it checks for the restricted interface before or after the other check...
@this That actually makes some sense. The interface isn't making assumptions about the strength of the typing in the calling code. Isn't everything VARIANT in VBScript?
so yeah, you really can't mix primitives in the property procedures. But you could mix object types because again, VBA has no idea about the object hierarchy.
it won't guarantee that VBA.Collection is castable to DAO.Recordset. that'll have to wait until runtime.
but yes it's borked.
probably because Microsoft had some PHP kids working on it, who knows.
Yeah -- Recall there's an open issue for case where the Nothing is dispatched through different types with no runtime errors whatsoever. But pass not-Nothing => RTE13.
@ITImpactInc I'm all for improving the VBE, but this is an objectively very terrible and backwards idea with horrendous implications. Please don't do this.
[7/12/2018 5:20:55 PM Informational] NUnit Adapter 3.10.0.21: Test execution started [7/12/2018 5:20:55 PM Warning] Exception System.IO.FileNotFoundException, Exception thrown executing tests [7/12/2018 5:20:55 PM Warning] Could not load file or assembly 'System.Xml.XPath.XmlDocument, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. [7/12/2018 5:20:55 PM Warning] at NUnit.VisualStudio.TestAdapter.NUnit3TestExecutor.RunAssembly(String assemblyPath, TestFilter filter)
PSA: Don't work off ActiveSheet. ActiveSheet is Object, which means every member call is a late-bound IDispatch query on the object's vtable, i.e. recipe for error 438. Declare/use an actual Worksheet object instead, and enjoy IntelliSense and compile-time validation.
#VBA #Excel
> @daFreeMan Agreed. I've been using MZ Tools Code Library with expansion shortcut it works well - when I remember to use it. Was also trying to learn C# so played in VS for a while and thought I'd gone bat s..t crazy when I returned to VBA to discover auto-correct... Hopefully RD could bring something similar but without having to press the expansion shortcut... (just pressing SPACE &/or ENTER would be awesome).
VBA Rubberducking
VBA Rubberducking