Also, just got feed back from another source.
If you do a .SetFocus in the Form Show event then the TAB sequence will NOT be affected by calling another form from within a GotFocus.
Thanks to all.
Hmmmm, had to do some research to figure out what the Default property did. Never used it.
A significant part of this particular LARGE VFP software package dates back to 1986. Many of the users (old farts like me) still use the Enter key to move from field to field. Teaching them to use the...
I found the problem.
It is NOT Win 10 update. Thank goodness, that would have been a REAL problem.
Also, it happened on the Win 7 computer as well but I was in a hurry (actually working on another project while trying to identify this problem) and forgot that I had done a duct tape and baling...
It DOES NOT happen on a Win 7 I set up with the current version of the system.
It works as it should.
This is very troubling.
Any other ideas to try?
Oh and thanks for the feed back so far.
I agree something changed.
So far it has been documented on two win 10 computers. One on the company network running the exe off the server and one completely stand alone in my office.
I have a win 7 I will try it on and get back to you. Good idea.
The forms are part of a company wide management system. Each is called from other areas and also have the ability to open other forms etc.
They are not stand alone. Without the entire system you would not be able to experiment with it.
The key here is that this problem started out of the...
I put a wait window "focus is in the exit button" in the gotfocus event for the Exit button within cntnrButtons to verify where the focus went after discovering the click event happened if you pressed enter when the cursor did not show again.
No changes have been done to this area of the form...
Greetings,
This edit routine worked properly until about 2 weeks ago when a user noticed and reported this change in behavior. The problem may have started before that, but because the user can just click on an individual field, edit and then save, the tab sequence change would not have been...
Changing the way the data is stored in the field would then require changing the code that uses the data to put together the parts list.
Its been running smoothly since the early 90s and I don't want to screw up a good thing.
Have fun, thanks again.
Clyde
This data is used in a production operation. The user is creating a custom device with many variations. He enters the guidelines such as measuring range and measuring type. The program then accesses multiple tables to pick the primary device and the components that fit that specific device to...
It is set to right middle.
As in .text1.alignment=1
So, it displays properly, but is saved with left alignment.
The indexing requires right alignment for proper display.
Thanks,
Clyde
Hello,
I have a table with a character field that needs to be right justified after a user enters data.
It is displayed in a grid using a textbox. Previously this field was accessed using the @...get routine
with the FUNC "J" clause for right justification. This then saved the data to the...
Ah, finally I understand! Sometimes it takes awhile.
The only guaranteed way to make a grid completely readonly is to make the column1.controlsource an expression instead of a field.
To me readonly meant READONLY! I don't allow editing in a grid, I always have the user highlight then click an...
Yes I know that ANYTHING can be forced to display in a grid.
The issue and the concern is that the GRID saved data to a table on its own volition.
Clyde
Oops! Forgot this part.
NOW go back in TEMP.prg
and add parenthesis as below:
Dimension m_gridcols(2,2)
m_gridcols(1,1)="HD iID"
m_gridcols(1,2)="(iID)"
m_gridcols(2,1)="HD cText"
m_gridcols(2,2)="(cText)"
and the blanking problem disappears.
Hello and thanks for your response.
.VALUE="" is in the code that was beautified above, look for this:
*?m_columntext
With Thisform.grdList.&m_columntext
.Enabled=.F.
.ReadOnly=.T.
.Value="" &&m_value
.FontName="FOXFONT"
.FontSize=12
Endwith
Endf...
Had a few minutes so,
Below is code that duplicates the "blanking a field and saving it to a table" behavior:
In TEMP.PRG paste:
Create Cursor curTest(iID c(5), cText C(12))
For i = 1 to 8
Insert into curTest (iId,ctext) VALUES (STR(i,5),STR(i*2.7,12))
EndFor
IF file("curtest.dbf")
DELETE...
Yes, your test works in VFP8.
Yes, I am sure the fields are blanked and written back to the table.
After doing some more experimenting, this is what I have found.
Using the original code (please reference the beautified version supplied by Danfreeman above) I was using FOR to step through the...
Thanks for the responses.
danfreeman:
Under NO circumstances should "Do"ing a form blank fields in a database. That is scary behavior. The grid is READONLY.
The form is not opening or closing a table.
Where is the documentation for this known behavior? I could not find it.
OlafDoschke:
Your...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.