SQLTalk 12.0.0 64-Bit Not Registered/Error Opening file.SQL

[Clifford Bass]

Hi,

Just installed SQLBase 64-bit, complete, on a new machine (virtual; Windows Server 2012 R2 Standard, fully patched). When I double-clicked on the error.sql file it indicated no program was defined for opening .sql files. Choosing SQLTalk.exe as the program to associate with .sql files produced the error "Encountered an improper argument."; but then opened the file anyway. Subsequent instances of double-clicking on a .sql file produces the error and opens the file.

Clifford Bass

[Mike Vandine]

Hi Cliff,

I'm not sure why SQLTalk would even allow you to open a file as the default program. I know that there are parameters that you can specify when running SQLTalk, i.e. BAT, etc. but I don't know why it would actually open the sql file. I always default my .sql files to notepad or similar.

Did this work with previous versions of SQLBase?

Best regards,

[RainerE]

I'm always opening wts files with SqlTalk by double clicking on the file. For me this works with SQLBase 9.0.1 and 11.0.2.
Regards,
Rainer

[Clifford Bass]

Hi Mike,

As with Rainer, I have always been able to open .SQL files by double-clicking on them; and frequently did so. This is up through 11.6.x. With 11.7.x I had to associate the .SQL with the SQLTalk program; but once it was associated it worked fine. As noted, it still works even with 12.0.0, but it gives the error every time a file is opened by double-clicking.

Cliff

[Mike Vandine]

OK. I'll check on this. I've just never associated .sql with SQLTalk. Ya learn something new every day!

Cheers!

Mike

[Clifford Bass]

Thanks Mike!

The association was done by the installation programs for many years; until it seems with 11.7.

Amazing what one learns. We get into a habit of doing something one way and then get a surprise when we see or hear of a different way.

Cliff

[Mike Vandine]

Hi Cliff,

The error that I get is 'Unable to communicate with SQL Daemon. Ensure that daemon32.exe is in a directory on the path. Once I clear that, then the file pops up in the SQLTalk window.

I have tried putting in a path statement, making sure the daemon.32.exe is in the same directory as the SQLTalk.exe, put it in \windows\system32 and it always returns this message.

Where do you have your daemon32.exe located?

I checked with the Developers this morning and they assure me that an automatic association of .sql files to SQLTalk has *never* been done with the installations. If you already had this association in place when you did the install, it would still be in place (a Windows thing).

Cheers!

Mike

[Mike Vandine]

Hi Cliff,

OK, scratch that first bit. I set up the association for the SB11.6 version of SQLTalk and that worked fine. I then modified the association to point to the 12 version, but apparently Windows remembers previous associations even though you change the file to open. I fixed the command in the registry for the association to point to the 12 version of SQLTalk and I get the same message that you do.

I will log a defect.

Cheers!

[Mike Vandine]

BTW, if you try to run SQLTalk from a cmd line using the same parameter as what is set up in the association, you get the same error. For example:

>c:\sb1264 sqltalk.exe "error.sql"

Gives you the error then starts up SQLTalk with the error.sql file.

[Mike Vandine]

I created SQLB-2448 for this issue.

Cheers!

[Clifford Bass]

Hi Cliff,

.....

I checked with the Developers this morning and they assure me that an automatic association of .sql files to SQLTalk has *never* been done with the installations. If you already had this association in place when you did the install, it would still be in place (a Windows thing).

Cheers!

Mike

Hmmm,... I could be that I have always been double-clicking .sql files and when a new installation has been done and associating it when prompted. But that is not my memory. But my memory could be fading..... or messing with me.

Oh well...

[Clifford Bass]

I created SQLB-2448 for this issue.

Cheers!

Thanks Mike!