Author Topic: ThumbsPlus 7 : MySQL database : Part 1 (Read 4547 times)

wingfield · « **on:** 2014-08-16 20:55:56 »

hello all,

well - as luck would have it, my computer crashed in a recent thunder storm. I've been busily reloading all my software for the past few days. I've now gotten around to the difficult stuff. I consider TP7 difficult. before the crash, I had successfully created a MySQL db for TP7 and was using TP7 Pro sp2; having been reluctant to move to either TP8 or TP9 based on forum comments.

well, up to this point, I've not been able to successfully get TP7 to work again with MySQL. I hope to get some assistance on this forum. Here's what I've done so far. I've gone from memory as well as making use of a very old post from the Cerious Archives by Chris Williams. I've gone ahead and posted this in it's entirety at the bottom of my post for other folks reference -as I've found it quite helpful in reconstructing TP7 with MySQL.

I'm running Win7 Home Premium 64 bit sp1 with 8gig memory

so, here's what I've done so far.

(a) installed MySQL Community Server v5.6.2 (not sure if relevant; but before my crash, I was using an older version)
(b) installed Workbench v6.1 (not sure if relevant; but before my crash, I was using an older version)
(c) ensured MySQL service is running
(d) restored my backup dump files for my ThumbsPlus db in Workbench (yep, I had a backup). I can connect to the Thumbs db in Workbench and I can see the tables in Workbench as well. My data looks fine.
(e) installed 32 bit ODBC. yep, somehow I managed to remember that TP7 is 32 bit and since I'm running Win7 64 bit, I had to install ODBC 32 bit for TP7 to see the ODBC data source.
(f) created the ThumbsPlus ODBC data source in the 32 bit ODBC.
(g) ensured that I have appropriate permissions to the schema within Workbench.
(h) changed the SQL_mode to 'ANSI' in the my.ini file.
(i) verified in Workbench that SQL_mode is set to 'ANSI'. It is.
(j) run TP7. choose "file / database / connect / machine data source/ thumbs
(k) get the following error message :<)

does anyone have any thoughts on what the problem is here?? I'd sure love to be able to get back to where I was before my laptop crashed.

thank you in advance for any help provided.

because of the 5000 character post limitation, I need to put the 5/21/2007 post from Chris Williams in a 2nd post. sorry about that.

Daan van Rooijen · « **Reply #1 on:** 2014-08-16 22:23:48 »

Hi David,

Thanks for the kind words in the other message!

Have you tried running as an administrator? I don't know about Workbench but TP needs read and write access.

If the database is on a server, have you set MySQL to ansi mode there, too?

Could you try this line in my.ini - it may be required by newer versions of MySQL?:

sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,ANSI_QUOTES"

Finally, could this be relevant: http://forums.cerious.com/forum/index.php?id=435 ?

You may also want to search the newsgroup archives for '8038' :)

wingfield · « **Reply #2 on:** 2014-08-17 16:15:35 »

Daan,

I thank you again for jumping in with some suggestions. unfortunately, none of those worked.

anyone else have any ideas?

is it possible that TP7 only works with an older version of the 32 bit ODBC driver I'm using???

I'm open to all suggestions.

best regards,

David

Daan van Rooijen · « **Reply #3 on:** 2014-08-17 17:36:22 »

> I thank you again for jumping in with some suggestions. unfortunately, none of those worked.

Too bad. I've never dabbled with MySQL myself, so I can only reproduce what others have said about similar cases in the past. A final suggestion from my part is that you could turn SQL tracing on in Control Panel / Administrative Tools (Data Sources icon) to see the conversation between TP and ODBC around the time when the error occurs.

wingfield · « **Reply #4 on:** 2014-08-17 17:58:37 »

Daan,

thank you again for the response. I've pasted below parts of the ODBC log (it's 290k characters and there's a 5000 character limit) that you suggested running a trace for. it's a lot of gobblygook; but maybe someone will understand parts of it.

best regards,

david

Thumbs 778-2b24   ENTER SQLAllocHandle
      SQLSMALLINT 1
      SQLHANDLE 0x00000000
      SQLHANDLE * 0x030E061C

Thumbs 778-2b24   EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
      SQLSMALLINT 1
      SQLHANDLE 0x00000000
      SQLHANDLE * 0x030E061C ( 0x03818638)

Thumbs 778-2b24   ENTER SQLSetEnvAttr
      SQLHENV 0x03818638
      SQLINTEGER 200
      SQLPOINTER 3
      SQLINTEGER 0

Thumbs 778-2b24   EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
      SQLHENV 0x03818638
      SQLINTEGER 200
      SQLPOINTER 3
      SQLINTEGER 0

Thumbs 778-2b24   ENTER SQLAllocHandle
      SQLSMALLINT 2
      SQLHANDLE 0x03818638
      SQLHANDLE * 0x030E0620

Thumbs 778-2b24   EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
      SQLSMALLINT 2
      SQLHANDLE 0x03818638
      SQLHANDLE * 0x030E0620 ( 0x038186B0)

Thumbs 778-2b24   ENTER SQLSetConnectAttr
      SQLHDBC 0x038186B0
      SQLINTEGER 103
      SQLPOINTER 60
      SQLINTEGER 0

Thumbs 778-2b24   EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
      SQLHDBC 0x038186B0
      SQLINTEGER 103
      SQLPOINTER 60
      SQLINTEGER 0

Thumbs 778-2b24   ENTER SQLSetConnectAttr
      SQLHDBC 0x038186B0
      SQLINTEGER 101
      SQLPOINTER 0
      SQLINTEGER 0

Thumbs 778-2b24   EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
      SQLHDBC 0x038186B0
      SQLINTEGER 101
      SQLPOINTER 0
      SQLINTEGER 0

Thumbs 778-2b24   ENTER SQLSetConnectAttr
      SQLHDBC 0x038186B0
      SQLINTEGER 108
      SQLPOINTER 2
      SQLINTEGER 0

Thumbs 778-2b24   EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
      SQLHDBC 0x038186B0
      SQLINTEGER 108
      SQLPOINTER 2
      SQLINTEGER 0

Thumbs 778-2b24   ENTER SQLDriverConnectW
      HDBC 0x038186B0
      HWND 0x00000000
      WCHAR * 0x53378B34 [ -3] "******\ 0"
      SWORD -3
      WCHAR * 0x53378B34
      SWORD -3
      SWORD * 0x00000000
      UWORD 0

Thumbs 778-2b24   EXIT SQLDriverConnectW with return code 1 (SQL_SUCCESS_WITH_INFO)
      HDBC 0x038186B0
      HWND 0x00000000
      WCHAR * 0x53378B34 [ -3] "******\ 0"
      SWORD -3
      WCHAR * 0x53378B34 [-3]
      SWORD -3
      SWORD * 0x00000000
      UWORD 0

      DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)

      DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)

Thumbs 778-2b24   ENTER SQLAllocHandle
      SQLSMALLINT 3
      SQLHANDLE 0x038186B0
      SQLHANDLE * 0x030E0648

Thumbs 778-2b24   EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
      SQLSMALLINT 3
      SQLHANDLE 0x038186B0
      SQLHANDLE * 0x030E0648 ( 0x013BF708)

Thumbs 778-2b24   ENTER SQLAllocHandle
      SQLSMALLINT 3
      SQLHANDLE 0x038186B0
      SQLHANDLE * 0x030EAA08

Thumbs 778-2b24   EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
      SQLSMALLINT 3
      SQLHANDLE 0x038186B0
      SQLHANDLE * 0x030EAA08 ( 0x013BFA30)

Pete Wieland · « **Reply #5 on:** 2014-08-18 08:22:59 »

I had a similar problem with the newer versions of MySQL, and it is something I never got to the bottom of.

In the end I went back to a much earlier version of MySQL server (pre-Workbench version), got TP working with that and then upgraded MySQL. This worked for me.

I have had many problems with MySQL Workbench, and preferred the older utilities. I still use the old version of MySQL notifier. It sits in the system tray, I can right click and stop and start the server, configure instances and invoke the SQL editor. It is very simple, but it just works.

wingfield · « **Reply #6 on:** 2014-08-23 10:57:25 »

Folks,

I appreciate the replies so far. unfortunately, nothing has worked.

I'd like to ask for some information. if any of you have TP7 successfully installed with MySQL, could you please share the following??

(a) MYSQL version
(b) MYSQL ODBC connector version
(c) Workbench version
(d) copy of the SQL script you used to create the database.

thank you for the help

David

Sjoinca · « **Reply #7 on:** 2014-08-23 18:01:00 »

Mysql Server 5.6.17 on Win 64
Mysql ODBC 5.3 Unicode Driver version 5.03.02.00 Using "system data source"
Mysql Workbench 6.1, and SQLyog
SQL script. I created my database in 2006 before Phillip posted his version on the website. I used Mysql rather than the InnoDB file system.

I think you should use the scripts provided by Phillip at http://www.cerious.com/databases.shtml.
I made script mods (tweeking storage sizes for some table items, I didn't keep track of my mods)that may make upgrading to the V9 or 10 database difficult. I have not tried upgrading yet.

Steve

wingfield · « **Reply #8 on:** 2014-08-25 19:01:56 »

Sjoinca,

thank you for the response. well, I've gotten everything installed as per the versions you've shared and I'm still getting the same error. very frustrating. I can see the tables fine in workbench. I can write SQL queries against the tables and they work fine. the TP7 sp2 software still thinks something is wrong.

any other thoughts from anyone???

are there any diagnostics I can do to chase this? I've posted part of the ODBC log. would the entire log be of benefit?

let me add another thought. since my machine crashed, I had to reload the operating system to factory image. I named my computer exactly the same; but I'm wondering if some of the stuff in the volume table is causing a problem (ie: serialno, netname, etc??)

David

News:

Author Topic: ThumbsPlus 7 : MySQL database : Part 1 (Read 4547 times)