Forum Replies Created
-
AuthorPosts
-
-
January 18, 2023 at 10:33 #56967
Marco
ParticipantOr maybe you can give me documentation about it…
-
January 5, 2023 at 11:26 #56909
Marco
ParticipantSorry I forget to mention the version :
– kbmMW 4.11.0 Entreprise Edition
– kbmMemTable 7.23 Entreprise Edition
Thank you
-
January 11, 2023 at 09:03 #56947
Marco
ParticipantIf I define AutoFieldDefsOnOpen = mwafoWithData on client and server side, I have no issue BUT I have the same behavior (too much calls) as I said at the beginning of this post.
I put the code of my StoredProc, maybe I miss something :
Client side :
object spLoadShipping: TkbmMWClientStoredProc
ClientAsTemplate = False
QueryService = ‘MYMSSQLQUERY’
QueryServiceVersion = ‘1.0’
CacheParams = ptUnknown
CacheFlags = []
SessionName = ‘MSSQL’
ConnectionPool = MyConnectionDM.MyToolClientConnectionPool
StoredProcName = ‘SP_LOAD_SHIPPING_TEST’
Overload = 0
Params = <
item
DataType = ftInteger
Name = ‘@RETURN_VALUE’
ParamType = ptResult
end
item
DataType = ftString
Name = ‘@TEST’
ParamType = ptInput
Value = ‘test’
end
item
DataType = ftInteger
Name = ‘@ERROR_ONLY’
ParamType = ptInput
Value = ‘0’
end>
TransportStreamFormat = MyConnectionDM.MyToolBinaryStreamFormat
FetchLargeFieldsOnDemand = False
LargeFieldSize = 256
FetchMaxRecords = 0
KeyFields = ‘SHP_DIEZ’
TableName = ‘SHIPPING’
OnResolveError = spLoadShippingResolveError
AutoResolveOnChange = False
AutoResolveOnClose = False
AttachedAutoRefresh = True
AttachMaxCount = 1
AutoFieldDefsOnOpen = mwafoNever
FieldDefs = <
item
Name = ‘SHP_DIEZ’
DataType = ftString
Size = 10
end
item
Name = ‘SHP_NUM_DIEZ’
DataType = ftInteger
end>
IndexDefs = <>
SortOptions = []
PersistentBackup = False
ProgressFlags = [mtpcLoad, mtpcSave, mtpcCopy]
LoadedCompletely = True
SavedCompletely = False
EnableVersioning = True
FilterOptions = []
Version = ‘7.23.00 Professional Edition’
LanguageID = 0
SortID = 0
SubLanguageID = 1
LocaleID = 1024
BeforePost = spLoadShippingBeforePost
OnCalcFields = spLoadShippingCalcFields
Left = 28
Top = 16
object spLoadShippingSHP_DIEZ: TStringField
FieldName = ‘SHP_DIEZ’
ProviderFlags = [pfInWhere]
Size = 10
end
object spLoadShippingSHP_NUM_DIEZ: TIntegerField
FieldName = ‘SHP_NUM_DIEZ’
ProviderFlags = []
end
endServer Side :
object MyMSSQLStoredProc: TkbmMWADOXStoredProc
SessionName = ‘MYMSSQL’
ConnectionPool = MyServerDataModule.MyMSSQLConnectionPool
CacheParams = ptUnknown
CacheFlags = []
AutoFieldDefsOnOpen = mwafoNever
Resolver = MyMSSQLResolver
KillConnectionOnException = True
DesignActivation = True
AttachMaxCount = 1
AttachedAutoRefresh = True
EnableVersioning = True
IndexDefs = <>
SortOptions = []
ProgressFlags = [mtpcLoad, mtpcSave, mtpcCopy]
FilterOptions = []
LanguageID = 0
SortID = 0
SubLanguageID = 1
LocaleID = 1024
Params = <>
LockType = ltUnspecified
endMaybe it’s also because we don’t have the latest version of KbmMW ? I’m quite lost, if I try the test with an other component like the native ADOStoredProc, I have only one call on SQL Server database.
-
January 10, 2023 at 15:52 #56936
Marco
ParticipantHello Kim,
Thanks for your help, I tried to put AutoFieldDefsOnOpen = mwafoNever on client and server side, the problem is that we don’t define fields on the server side (as you explained). This cause an exception on the client side (Parameter @TEST not found). To summarize what I’ve done :
Client side : TkbmMWClientStoredProc.AutoFieldDefsOnOpen = mwafoNever (mwafoAlways before) -> Delete the first three calls to the server (no any more error)
Server side : TkbmMWADOXStoredProc.AutoFieldDefsOnOpen = mwafoNever (mwafoAlways before) -> Raise an exception (Parameters @TEST not found) on the client side.
When on the server side we had AutoFieldDefsOnOpen = mwafoAlways , I noticed that we had already this error on SQL Server side but not raised on the client side (so it was completely transparent for the user), now with mwafoNever , it’s not.
-
-
AuthorPosts
