Incompatible FileOpenDialog and _SQLite_Exec

[hname]

Hello,

This is my first post on Autoit forum.

I encounter a error when I select a csv file from FileOpenDialog  and convert it to db using _SQLite_Exec. The error code return is 1 if use both functions together. It works if I remove FileOpenDialog and use file directory.

The code and sample are attached( test.au3,sample.csv)

Anyone can help, please?

[jchd]

Your code lacks error checkings. You should check @error after every call capable of failing.

For instance, if the subdir ...\Repair_Projects\ doesn't exist, your code fails.

Also when testing for a row with a given imei, if the row doesn't exist, the result $imeirow is not an array. Yet you test $imeirow[0] without checking first.

BTW you don't need to startup/shutdown more than once. Same for open/close the DB.

[hname]

30 minutes ago, jchd said:

Your code lacks error checkings. You should check @error after every call capable of failing.

For instance, if the subdir ...\Repair_Projects\ doesn't exist, your code fails.

Also when testing for a row with a given imei, if the row doesn't exist, the result $imeirow is not an array. Yet you test $imeirow[0] without checking first.

BTW you don't need to startup/shutdown more than once. Same for open/close the DB.

Thanks.

Those you mentioned I can fix later (as it is a sample code). Let assume my code runnable (it actually run if you just set the correct directory). The thing is whenever I use _SQLite_Exec right after FileOpenDialog , the _SQLite_Exec  return @error code 1. That's very annoying. It run perfectly if you put $projectFile to the file directly.

 

[jchd]

I did run your code but then no error, except that I removed obviously failing lines. Yet there are a large number of open issues or bugs with the code as it is.

[hname]

16 minutes ago, jchd said:

I did run your code but then no error, except that I removed obviously failing lines. Yet there are a large number of open issues or bugs with the code as it is.

It's weird. I run my code on three different computers and get the same error code. if you don't mind, could you please upload your code. 

Thank you for your suggestion. Actually, I am not a coder. I just use autoit code to automate my work and it makes my life and everyone in the company I worked for dealing with data and report processing. I am not proud about my code as I know it is clumsy. The things are I can code what I thought in the way I want and the code works well and help reducing time and company running cost. 

Thank again.

[jchd]

6 hours ago, hname said:

I run my code on three different computers and get the same error code.

Instead, run the code you posted above verbatim and look.

[hname]

57 minutes ago, jchd said:

Instead, run the code you posted above verbatim and look.

I know now why my code led  to @error code 1 (Error calling SQLite API 'sqlite3_exec'). I tested three cases:

1. If I run my old code without FileOpenDialog , it works without issue.

2. If I run my old code with FileOpenDialog , it will give @error code 1 (Error calling SQLite API 'sqlite3_exec').

3. If I put the _SQLite_Startup() before  FileOpenDialog , it works without issue.

So, I think I found a bug in Autoit Sqlite API. When you put SQLite_Startup()  command after FileOpenDialog, it will give rise to SQLite API calling error.

[Jos]

8 minutes ago, hname said:

FileOpenDialog

...changes the workdir, so guess that could be the reason.

[jchd]

What @Jos just said (the SQLite.dll isn't found in @WorkingDir), plus you have lines in your code invoking undeclared variables GUICtrlSetData($StatusLabel,"Updating " & $imei) and other nasties (the first line of the .csv is ignored), close to zero error checking, etc.

When you post example code, please make sure it's runable in any other environment so we can test without spending time to fix it.

 

[hname]

1 minute ago, jchd said:

What @Jos just said (the SQLite.dll isn't found in @WorkingDir), plus you have lines in your code invoking undeclared variables GUICtrlSetData($StatusLabel,"Updating " & $imei) and other nasties (the first line of the .csv is ignored), close to zero error checking, etc.

When you post example code, please make sure it's runable in any other environment so we can test without spending time to fix it.

 

Got it. Do my best next time.