![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
#12
| |||
| |||
|
|
Bill, I'm not sure, do you still have a problem or is everything solved? |
|
Do you have the creation of the table in the OPEN or the INIT of the form? If you put it in the INIT method I can't understand why your current workaround should be needed? |
|
But probably I'm missing some thing. |
#13
| |||
| |||
|
|
What I have is working fine. I was just reporting what I had done to solve the problem. |
|
One possible problem with creating the table in INIT is that I couldn't open the form for design unless the table exists. With my current design, I can. |
#14
| |||
| |||
|
|
What I have is working fine. I was just reporting what I had done to solve the problem. OK One possible problem with creating the table in INIT is that I couldn't open the form for design unless the table exists. With my current design, I can. Yes, but you only need to run the form once. |
|
I often create temporary tables in the INIT, especially when working with an SQL-backend, and I don't encounter any major problem with it. |
#15
| |||
| |||
|
|
Yes, but you only need to run the form once. Not true. The form has function other than just creating the table. The form is an aid for solving Sudoku puzzles. It does the bookkeeping for you, but doesn't solve it for you. The table stores partial solutions for later attempts at solving. |
#16
| |||
| |||
|
|
Yes, but you only need to run the form once. Not true. The form has function other than just creating the table. The form is an aid for solving Sudoku puzzles. It does the bookkeeping for you, but doesn't solve it for you. The table stores partial solutions for later attempts at solving. OK, I can't really picture a situation where creation in OPEN *will* work and a creation in INIT will *not*. |
|
Anyway the important thing is that you found a solution that works for you. |
![]() |
| Thread Tools | |
| Display Modes | |
| |