Hi ALL,

I am playing with CursorAdapter Builder, and that of the DataEnvironment. VFP seems to generate some code in the AutoOpen and Init events like the one below (This is found in the INIT of a CA class I am doing):

*** Setup code: DO NOT REMOVE
local llReturn
do case
	case not pemstatus(This, '__VFPSetup', 5)
		This.AddProperty('__VFPSetup', 0)
	case This.__VFPSetup = 1
		This.__VFPSetup = 2
	case This.__VFPSetup = 2
		This.__VFPSetup = 0
		return
endcase
set multilocks on
llReturn = dodefault()
*** End of Setup code: DO NOT REMOVE

*** Setup code: DO NOT REMOVE
if This.__VFPSetup = 1
	This.__VFPSetup = 2
endif
return llReturn
*** End of Setup code: DO NOT REMOVE

Another is the 'inconsistent' behaviour of the CA builder in 'injecting' the connection string. After saving the CA class, one finds the connection info gone again!

At times, you can see the connection string (dsn=test;uid=root;pwd=12345) in the Tag property. At times, an SQLSTRINGCONNECT statement will be found in the Init.

Thus, my Questions:

Question 1:
What is its purpose? What are the implications if I remove them in the creation of my own CA subclass?

Question 2:
Have I missed a pattern with regards to the 'inconsistent' behaviour in 'injecting' connection string info?

Question 3:
Any links that documents event sequence of DataEnvironment with CursorAdapters?

Question 4:
Does answer to #1 also apply to DE's with VFP tables or a mixture with CAs?

Thanks in advance.


Dennis