select {open filename] works fine native, but gives 107 operator operand mismatch in .exe

[CJMK]

Had similar issue on opening table, getting index error, and got around that by reindexing at first open. Now a very short time later, in init, I select it, and it gives me the 107.
I am compiling with innosetup. It also is not finding another table and forcing me to locate it (right where it is supposed to be, and in the path.

 

[Chris Miller]

What's the line of code?

Because I can't reproduce error 107 from USE or SELECT-SQL. Also not from SELECT workarea. In that case workareas are "plain" following the name pattern rules of VFP. Usually they reflect the stemname of a table, yourtable.dbf is gettin workarea alias yourtable, there is no path portion and if the file name contains spaces they become underscores in the alias name.

But all that said, at most a select with a wrong name gives a syntax error or just alias is not found, not 107 operator/operand type mismatch.

Chriss

 

[Mike Lewis]

You need to give us more details. As Chris said, we need to know at least what code is throwing the error.

As far as not finding the table is concerned, could this be the same problem that you described in thread184-1814069? If so, you received several answers to your post there that should help. It should never be necessary to recreate the index each time you open the table.

In any case, error 107 has nothing to do with indexes. That's why we need to see the code.

Finally, you said you are "compiling with innosetup". InnoSetup is not a compiler. It is a tool for creating an installation program (SETUP.EXE). It is VFP that does the compiling.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[Chris Miller]

Yes, I also pointed out that innosetup isn't the VFP compiler in the older thread.

If you change code and then use inno setup to create a new setup, that doesn't change anything, as usually inno will only take the EXE file and data files etc., but no source code files from a PJX to aseemble a setup exe, changes in code have to be compiled into the EXE by VFP and then that gets into the setup by using inno.

Chriss