Eduardo,
I'm really not sure what the batch update option does on a remote view. It seems like records would have to be updated in a remote view, but I'm not sure. Maybe someone else can answer this.
If you set the number of records to fetch at a time to -1 (all), VFP will send the query to to back end then wait until all requested records are returned before returning execution to your program. If you set this to anything else (let's say x), VFP will send the query to the back end then wait until all records are returned or x records are returned (whichever is smaller) before returning control to your program. Once control is returned to your program, VFP will continue to add x records at a time to your view as they are received from the back end until all records are received. An example of how this may be useful is if you wanted to display the view in a grid or browse and wanted to display the records as they became available. You should be aware that setting this to anything other than -1 will cause the view to execute asynchronously (see below for what kind of problems this may cause).
The maximum number of records to fetch sets the maximum number of records that VFP will fetch from the back end. So if you set this to 1000 and your query returns 5000 records, your view will only contain the first 1000 records. You should know that the back end will run the entire query, the only thing this setting affects is how many records VFP brings back from the query results.
Use memo when character field length >= x is used to determine how large a character field is before VFP makes it a memo field. This is useful because many databases support character fields >254 (VFP's limit). You'll generally want to leave this at its default of 255 so that character fields will be used when possible and memo fields will be used when needed.
Share connection determines whether the view will share a connection to your back end database with other views in the database that are also set to share connection. Keep in mind that each connection in this case is really an instance of the connection you define in the database. Each connection takes up resources on the server so it's often a good idea to share them. You should know that you can only execute one command at a time over a single connection. This means that views running asynchronously (either because your fetch size is not set to fetch all records at once or because your connection is set for asynchronous execution) should not share a connection.
If you set you connection for asychronous execution, control will return to your program before all of the records have been received from the back end. I don't think it applies to views (I think it's really the number of records to fetch at a time setting that determines this for view), but it does apply to SQL pass-through which uses SQLCONNECT(), SQLEXEC(), etc. to send commands to the back end. Take a look at the help for SQLEXEC() for more info on how to handle asynchronous execution with SQL pass-through.
Hope this helps,
Josh
>I read that but I need more information about the batch update, all the fetch options, and also about the share and about the asynchronous execution in the Connection itself.
>
>>Look in the VFP help under "Advanced Options Dialog Box" (in the US English version). It gives a pretty good description of what the options do. If you have any specific questions, ask them here. I'm sure someone will be able to help you.
>>
>>>Does anyone know if there is a place in the Web with documentation of how really work all the settings in the Advanced Options of a remote view (menu Query, option Advanced Options). I'm getting more and more confused with these.
>>>Thank you.
