Submitted by jdonlan on 2009/04/07 15:47
 I'm trying to import / synch data from an internal MySQL database. I've configured a SQLSynch.xml file with  the field mapping and so on but I can't make the connection with the database. I'm currently running with no password to eliminate that as a problem but whatever connection string I try, I end up with a
"Cannot connect to server (Application-defined or object-defined error)"
message box.
I can connect with MySQL Administrator (for example) using the same parameters from the same machine.
I can create a System DSN using the MySQL ODBC driver on this machine using the same parameters.
Is there some way I can get more meaningful error messages from IQ to help troubleshoot this connection?
Running IQ Version 0.9.24 Pre-release 10 build 04/06/2009 3:44:38 PM 
Thanks,
John 
 

Comments

Great to see users trying advanced features!
 
Have you tried using your DNS connection ?
 
<connectionstring>"DSN=DSNTest;UID=***;PWD=***;"</connectionstring>
 

jdonlan

2009/04/07 16:49

Permalink

Great to see users trying advanced features!
 Or trying to!
Exact same error using the DSN format (which is much easier BTW!), it just doesn't seem to be making contact with the database at all.
Again, doubled-checked the DSN connection with the "TEST" button and it was OK.
 
John

Pierre_Admin

2009/04/07 16:51

Permalink

Can you send the .xml file to betasupport@sqlnotes.... ?

gregory

2009/05/17 20:25

Permalink

More generally on this topic.
 
I have a significant number of small databases which I have created using originally Microsoft FoxPro and, more recently, Microsoft Access. I am careful to design these well, and they are fully normalised with many-to-many relationships implemented using compound primary keys. My intention is, over time, to move most of these over into IQ.
 
I understand that I can synch IQ fields with individual tables. However, I do not see how I should synch multiple, related tables.
 
How can I enforce referential integrity in IQ? Particularly with compound keys?
 
Also: is there some part of the documentation which I have missed which describes how best to plan an IQbase, particularly where the user understands the principles of relational database design?

Pierre_Admin

2009/05/17 20:39

Permalink

>However, I do not see how I should synch multiple, related tables.
Currently, you can sync only one external database per IQBase. This restriction will be lifted in an upcoming release.
 
>How can I enforce referential integrity in IQ? Particularly with compound keys?
While internally IQ uses a relational database (normalized with primary keys, etc), the concept behind IQ is different than databases. It is a free-form database (a record that can have any number of field values: a contact can have appointment info, etc)
 
So, while some database applications can be moved to IQ, not all, especially those with complex relationships. One should see IQ as a complement to relational database, being somewhat in between Excel (no structure whatsoever) and Access (very structured, sometimes lacking flexibility).
 
The best way to describe records in IQ (i.e. items) is: each item is like an individual, like you and me. We have relatives, but these links are not life-threatening. We can have many different groups of properties (or field values): physical (hair color, weight), contact (address, email), etc

gregory

2009/05/17 20:56

Permalink

I like the idea that IQ is intermediate in the structure that it enforces between spreadsheet and relational databases. The issues that brings are multiple, however. The huge advantage of a relational database is that in a well structured database, if you ask a well defined question, you get a precise answer. In Excel, it depends how carefully people have structured the data as to whether any sort of answer can be obtained at all.
 
In IQ, as in any personal or small group information management, the advantages the user can get out are proportional to the efforts he or she puts into structuring and storing the data well in the first place.
 
One of the contributions I would like to make to the success of IQ is helping to write documentation which describes "good" approaches to structuring user data (so that it is validated and, where appropriate, auto-assigned). But I can't run before I can walk, and I need to get much more into the program first!
 
I entirely agree that no one approach can answer every information management need. That said, marketing IQ well will involve positioning it carefully (and in a way which doesn't frighten off people who think and work intuitively and not hyper-analytically!).
 
In any event, thanks for such swift answers to this question and the one I asked concerning appointments.
 
Mark

Armando

2009/05/17 23:25

Permalink

> In IQ, as in any personal or small group information management, the advantages the user can get out are proportional to the efforts he or she puts into structuring and storing the data well in the first place.
 
This is entirely true. Structures I've carefully crafted over several weeks are incredibly efficient and expendable.
 
 
>One of the contributions I would like to make to the success of IQ is helping to write documentation which describes "good" approaches to structuring user data (so that it is validated and, where appropriate, auto-assigned). But I can't run before I can walk, and I need to get much more into the program first!
 
This is a subject I really enjoy...  I'm all for such documentation and I could help when I have more time.