Access2Base - tdf#136063 Workaround Basic missing argument handling

When an argument is missing in a call to a Basic function
the IsMissing() function applied on the argument
should respond True.
However sometimes(?) the argument contains instead "Error 448"
making IsMissing responding False.

This commit puts an explicit argument in the function call
avoiding the different behaviour of the Basic interpreter
in LO 7.0 vs. previous releases.

Change-Id: Ic90fb7ec9b6e520cc762a441ca383b54c5d4db16
diff --git a/wizards/source/access2base/PropertiesGet.xba b/wizards/source/access2base/PropertiesGet.xba
index 332eaaa..e6d481e 100644
--- a/wizards/source/access2base/PropertiesGet.xba
+++ b/wizards/source/access2base/PropertiesGet.xba
@@ -1017,7 +1017,7 @@ Dim sObject As String
	_hasProperty = False
	If Not Utils._CheckArgument(pvProperty, 1, vbString) Then Goto Exit_Function
	
	_hasProperty = Utils._InList(pvProperty, pvPropertiesList(), , True)
	_hasProperty = Utils._InList(pvProperty, pvPropertiesList(), False, True)

Exit_Function:
	Utils._ResetCalledSub(sObject & ".hasProperty")