Search results for query: *

My problem is that I thought that when a DB Profile was Exported from PB9 and Imported into PB10; that it changed the PB10 ini file. This is not the case- possible PB Bug!? While the new profile allows you to interact with the database and tables in the database painter; it doesn't change the...

The PB9 datawindows had to have the table re-connected to work; which solved the PB9 problems. PB10; however, is still dysfunctional.

Forgot to say- Once you install the plain vanilla version of PB out of the box - - - say PowerBuilder 9.0 . Then you should immediately go to the Sybase website and install the latest EBF's for that version. That's why my Powerbuilder versions were 9.02 and 7.03 - because we had installed...

We skipped PB 8.0 ( because it seemed to have problems ) and migrated our applications from PB 7.0 to PB 9.0 fairly easily ; except that the Interactive Development Environment changes between PB 7 and PB 9.0 . Therefore, in that case you should study 9 instead of 7 . Consideration also should...

In Migrating pbls from PB9 to PB10 the new PBL compiled OK and an exe was created. When it was run in the IDE it displayed the table data correctly. No data was saved or updated. Now the PB9 application gives a "Database Problem 2 select error database processing error" when it tries to display...

just 'borrowed' this code from a fellow company programmer ( I think works in PB6.5) 1. Get into your datasource. 2. Convert it to Syntax. 3. Add onto the end of the field retrievals 'c_checked' = ' ' 4. go back to the datawindow---you should find a new field called c_checked on it. 5...

I think I actually renamed the system.mdw file to system.backmdw; so that the Access97 app wouldn't be confused. You probably wouldn't want to have 2 *.mdw files there.

I am not an expert; except perhaps in some programming. I needed to look at the code in an Access97 app bought 'out of house'. Notice that both your application and Access97 by itself have a security file *.mdw . I re-named the system.mdw file in Access97 to a backup , say backiupsys.mdw ( so...

To PHV:- Thanks! ---Changing the query in interactive SQL will enable it to work; but I'm still left with the problem that ODBC doesn't do this for me!?

Thanks BNPMike! I'll have to try that. I'll also be glad to get any other suggestions for this problem from you and others!

Thanks PHV! I'll see if I can modify the Access query to be more acceptible to PowerBuilder. I was trying to leave those alone; as somebody else programmed the Access part; but I'll see if modifying them will make a difference. I'll also be glad to get any other suggestions for this problem...

I have an ODBC connection to Microsoft Access 97 Tables fropm PowerBuilder 7.03. However, when I try to Edit the Data of one of the Access tables from PowerBuilder it gives me the error SQLSTATE = 37000 [ODBC Microsoft Access Driver ] Syntax error in date in query expression 'order#'. SELECT...

Putting in the PowerBuilder Catalog tables seems to be the correct solution. Some interesting things:- PowerBuilder gives the Invalid Table/Column format message when it actually is an permissions problem, I.e., the tables were established under one userid and the access (pun!) application...

Thanks PowerObject However I want to use the PowerBuilder catalog tables, if at all possible. Interestingly, if I create new Access tables with PB compatible data types; I can then copy the access data table to table within acccess and then go back through...

One script established the PowerBuilder catalog tables in the Access Database ( which got rid of the 'Catalog Tables are not available' message ); however the Access tables were still not useable since none of the Access table information had been loaded into them, so they still gave the 2nd...

Thank You OlanKnight. I'll look this up as soon as I can ( however I have managed to temporarily miss-place the installation disks ).

Hi I need to connect the Powerbuilder development environment ( 7.03 ) to an MS Access97 DB and tables. What I have:- An ODBC connection ( which connects! ) However; I get the message 'Catalog tables could not be created and are not available for use'. This is reflected in the fact that...