drosenkranz
Programmer
Hello Again,
I have a form with a grid on it. The dataenvironment has a local view which works fine when the select statement was started as "Select *...". THE DATA IS STILL EDITABLE AT THIS POINT
I used the grid builder to change the order of the fields as they appear in the column but the fields still appeared in the same order as before, but the column headers were in the correct order. The CaseID column now had a date instead of the case...etc.
I rewrote the Select statement with the fields in the order I had designed the builder columns and everything came out alligned correctly. The problem is that I can not edit any data in the grid anymore. The .ReadOnly property of my grid is set to false. If I create a second (new) grid and link it to the local view, I can edit the data there.
Any info on what's causing (or how) the the "Builder" changed my original grid so I can no longer edit the data that appears in it?
As Always, Thank you all very much.
The 2nd mouse gets the cheese.
I have a form with a grid on it. The dataenvironment has a local view which works fine when the select statement was started as "Select *...". THE DATA IS STILL EDITABLE AT THIS POINT
I used the grid builder to change the order of the fields as they appear in the column but the fields still appeared in the same order as before, but the column headers were in the correct order. The CaseID column now had a date instead of the case...etc.
I rewrote the Select statement with the fields in the order I had designed the builder columns and everything came out alligned correctly. The problem is that I can not edit any data in the grid anymore. The .ReadOnly property of my grid is set to false. If I create a second (new) grid and link it to the local view, I can edit the data there.
Any info on what's causing (or how) the the "Builder" changed my original grid so I can no longer edit the data that appears in it?
As Always, Thank you all very much.
The 2nd mouse gets the cheese.