advantage-database-server

Our EMR software uses Advantage Database SQL server as its database and I'm creating various PHP projects which require interaction with this database. What is the best approach to connecting and working with Advantage DB SQL and PHP? I'd like to connect on a read-only level to prevent any data wrong-doing with insurance/patient/provider records. Note: I connect to other databases using PDO drivers. Is there an Advantage DB driver for PDO that I'm unaware of? Server info: PHP, Windows 2008, IIS 7 PHP PDO support is slated for release in v11.0 of Advantage later this summer. It is listed on our

I have a question on subqueries in advantage. As I was analyzing several SQL queries I stumbled upon a strange situation. When I executed the following SQL, I got these results: select * from orderlyn where OLWArtnr in (select OlwArtnr from prijs) But OlwArtNr doesn’t exist in the table Prijs. CREATE TABLE Prijs ( Nummer Char( 20 ), Lijst Char( 15 ), Verkprijs Double( 0 ), Aankprijs Double( 0 ), BTW Char( 2 ), Naam1 Char( 30 ), Naam2 Char( 30 ), Naam3 Char( 30 ), Naam4 Char( 30 ), Vervangnr Char( 20 ), Kortcode Char( 10 ), Datum Date, Vpeuro Double( 0 ), A1 Char( 20 )) IN DATABASE; What

I am converting a Delphi program from the BDE to Advantage Database. On weekends I work on a Win 7 machine using Delphi XE. During the week I work on a Win XP machine using Delphi 7. Advantage tables work fine on the Win 7 machine but when copied to the XP machine they cannot be accessed - Error 5175 the index was created with a different collation sequence I have searched the net, even gone into the Advantage forums but can't find anything helpful. The XP and Win 7 are both set up the same as regards location etc. Table properties lists the collation sequence as blank. Anyone know what is

Is using "view" in db design right method or we should handle it code side? What are the advantages or disadvantages? I see a couple of reasons to use views : Provide a simpler interface : just query the view, and not a dozen tables, doing joins and all Provide an interface that doesnt change (or less often) : Even if you change the structure of the tables, you might be able to modify your view so it still returns the same thing Which means no change is needed in your application's code : it'll still work, as it's using the view, and not directly accessing the tables Only provide an interface

As far as i can understand to use pyodbc you have to cnxn = pyodbc.connect('DRIVER={Advantage ODBC Driver};SERVER=local;DataDirectory=\\AltaDemo\Demo\AltaPoint.add;DATABASE=AltaPoint;UID=admin;PWD=admin;ServerTypes=1;') cursor = cnxn.cursor() This is the error i get from the console when i run this Error: ('IM002', '[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified (0) (SQLDriverConnect)') The name of the driver is Advantage StreamlineSQL ODBC , so the bare minimum connect string is: DRIVER={Advantage StreamlineSQL ODBC};DataDirectory=D:\Temp

Database: Sybase Advantage 11 On my quest to normalize data, I am trying to delete the results I get from this SELECT statement: SELECT tableA.entitynum FROM tableA q INNER JOIN tableB u on (u.qlabel = q.entityrole AND u.fieldnum = q.fieldnum) WHERE (LENGTH(q.memotext) NOT IN (8,9,10) OR q.memotext NOT LIKE '%/%/%') AND (u.FldFormat = 'Date') ; This is the DELETE statement I have come up with: DELETE FROM tableA WHERE (SELECT q.entitynum FROM tableA q INNER JOIN tableB u on (u.qlabel = q.entityrole AND u.fieldnum = q.fieldnum) WHERE (LENGTH(q.memotext) NOT IN (8,9,10) OR q.memotext NOT LIKE '%