VB I don t think it s thoughtful, please complete and optimize the prawns

With there seems to be nothing simplified at present.,This was originally Qiaosen for the sake of simplicity to write Min Pai Mu.。 The main thing is not knowing the specifics.

In addition, the load form3 sentence can be deleted, because the following one already contains load form3

The following let can be removed.

It's all about simplification!

The word let is not needed.

dim chkvalue() as integer

dim i as long,n as long 'long is the fastest; Repeating arrays is faster than repeatedly accessing elements.

redim chkvalue(

for i = 0 to ubound(chkvalue)

chkvalue(i)=

nextif = true and = true then

fff = false

for dd = 0 to 36

for j = dd + 1 to 36

for n = j + 1 to 36

if chkvalue(dd) = 1 and chkvalue(j) = 1 and chkvalue(n) = 1 then

if not (ww(dd) fff = true

goto go1

end if

end if

nextnext

next go1:

if fff = false then

iend if

end if

According to the logic of your program, it seems that as long as the check has a hook and the back judgment is really not deleted?

Abbreviated ideas:1Accessing arrays is much faster than accessing elements (. Especially if this kind of program is accessed frequently, it will speed up even more.

type loops are faster than unspecified type loops (32-bit processors).

3.Since as long as one matches the subsequent value, it will not change the value, so you can exit the loop directly.

4.Algorithm optimization. All three are accessed, so just 1 loop is all it takes.

And then the cycle resumes, because you don't have a lot of clarity, and I don't know exactly what it is.

1 lockwindowupdate lock interface refresh2 put this kind of processing into the module to speed up the processing3 I haven't used msflexgrid1, you can check if msflexgrid1 has a refresh event, if so, then false first after all the load is done and then true

4 Putting strings into variable processing speeds up processing.

You change the mid function to charat().

5-layer cycle, there are too many undersets, it's strange if it's not slow, take it apart and write.

The first layer of the loop is the split assignment, and it's nice for you to put the value into the array.

The second layer takes the value of the table unit in a loop, which can be embedded in it.

The innermost three loops don't have to be nested inside, it's better to take them out.

The key is whether your ideas are very simplified, it is recommended to paste your ideas up, and what problems to solve.

If there is no problem, there is no need to optimize, there are many reasons for optimization, if it is very slow, then change it, if there is no great improvement in program efficiency after optimization, there is no need to waste this time.

i + k + j = 0 can be changed to i = k = j

But it looks like it's a countdown shutdown program, and it's recommended that you use a timer, and the current time of the system will run along with the startup.

You yourself said yes, optimization doesn't help much, so don't waste that time