I have a query dataset with an AutoEdit of True and it is linked to a TGrid with a TGridColumn whose ControlType is ctEdit. The field is a Float.

In EWB's internal browser and a desktop browser in Windows, I can change the contents of the field and the change is reflected in the DBISAM table.

When running the application in Android, however, I am unable to change the contents of the field. The application will accept the entry but when I move the cursor down to the next row, the change does not "stick".

Is there some setting I should use for the Android and/or the IOS environment?

--
Frederick

Frederick,

<< Is there some setting I should use for the Android and/or the IOS environment? >>

Which browser are you using with Android ?  Chrome, or the default browser that came with the device ?

Tim Young
Elevate Software
www.elevatesoft.com

Frederick,

<< When running the application in Android, however, I am unable to change the contents of the field. The application will accept the entry but when I move the cursor down to the next row, the change does not "stick". >>

Also, does the problem occur when you simply move to the prior or next column, in addition to moving to the next row ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

/*
Which browser are you using with Android ?  Chrome, or the default browser that came with the device ?
*/

I am using the default browser that came with the device. With Chrome, it has the same issue.

--
Frederick

Tim,

/*
Also, does the problem occur when you simply move to the prior or next column, in addition to moving to the next row ?
*/

It appears that in Android, I can edit and change the value, if, the cell I am editing can be seen above the on-screen keyboard. For example, in the attached screenshot, the edit will be allowed if rows with values from 1 to 6 are double clicked or clicked if the query is in edit mode.

However, attempts to change values from 7 to 11 will result in the on-screen keyboard popping up and covering the cell being edited momentarily, and then pop down with the edit attempt aborted.

I think it is not so much the on-screen keyboard covering the grid but more so because, the grid's Stretch property is lsBottomRight and the grid shrinks upwards when the on-screen keyboard is shown, thereby hiding the cell being edited and causing the edit to fail.

--
Frederick

Frederick,

<< However, attempts to change values from 7 to 11 will result in the on-screen keyboard popping up and covering the cell being edited momentarily, and then pop down with the edit attempt aborted.

I think it is not so much the on-screen keyboard covering the grid but more so because, the grid's Stretch property is lsBottomRight and the grid shrinks upwards when the on-screen keyboard is shown, thereby hiding the cell being edited and causing the edit to fail. >>

Unfortunately, there's not much I can do about the Android keyboard causing layout issues.  Google, et al. decided to make the keyboard change the layout instead of being an overlay like Windows or iOS, and it's a big pain to deal with.

Tim Young
Elevate Software
www.elevatesoft.com