Ok, just take it easy! All 3 query functions give the same result (the query result window opens but only the background is displayed, no such text; in the window HTML source var resultJSON writes the correct results). That's the reason I talked about "generic" query.
Map file XY layer is the same as yours (I asked it some time ago) except for PROJECTION object that I commented out and for the connection line: "odbc://'':''/localhost a system_dsn||cities_cntrs||x,y,0"... what the last zero stand for? MS access db tied is composed by "cities_cntrs" table and lower case fields: x, y, city_name, admin_name. Respectevely double, double, text 50, text 50. My DSN is the same for the external joins. As I told you apache and php error logs don't warn anything, and pear connection is working surely because external joins are ok. What more? I don't know JS debugging, but, if this can be useful, my IE don't display any error message either in the main window and in the query window. Toni p.s. I think you need some holidays! ----- Original Message ----- From: Armin Burger To: toni-10 Cc: pmapper-users a faunalia.it Sent: Sunday, July 30, 2006 2:26 PM Subject: Re: [Pmapper-users] R: trying XY layer unsuccesfully The tests during development mainly used Postgres and SQLite for the xy layers, all 3 query types (identify, select, attribute search) are working for me, except the highlighting for the select. Attribute queries are not working correctly when the source is an MDB. The problem seems to be that even via ODBC MS Access does not understand standard SQL code. The query uses UPPER(searchfield) LIKE '%SEARCHSTRING%' and in case of Access it would probably need to be UCASE instead of UPPER. A satisfactory answer to your question is practically impossible because the problem description is again poor: no map file snippet, missing JS debugging info, 'query' is a term used for 3 different functions, etc. ===================================================================== I will just say this now and not every now and again that I will not any more reply to postings like this. There is a clear description in the Wiki FAQ how to describe a problem. But maybe no one has ever a look there... If folks don't take the time to investigate by themselves and write a decent description, they should not expect others doing this for providing support. Best regards armin toni-10 wrote: > more: > I checked the HTML source of the empty query result window (I can see only > the blue background) and I noticed that > var resultJSON it's correct: it contains everything (X Y and result fields) > > unfortunately nothing appears in the window >
