Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (8)

Resolved Running PowerBuilder 2019 Universal. Cannot connect to current database

  1. Issue
1
Votes
Undo
  1. Arthur Foux
    Arthur Foux
  2. PowerServer 2020 or older (Obsolete)
  3. Tuesday, 13 August 2019 21:08 PM UTC

This is the server we are using

The application loads. After the password is entered these are the messages that appear and I believe in this order.

 

This is AEM data source. There is only 4 items that appear in the ODBC Data Source dropdown. How do I get all of them to show as it does above?

  1. AEM
  2. Database
  3. DataSource
  4. SQL Anywhere
  5. SQL Server
How to Handle Flash File with use OlecustomControl...
Edit mask in PowerServer
Responses (8)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 13 August 2019 21:59 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Specifically for PowerServer connecting to SQL Anywhere on a 64-bit machine, you should try the following:

1. Use the native driver option rather than ODBC option in the AEM.

2. Make sure your system DSN is 64-bit instead of 32-bit.

Also, in the "Transaction Objects" section of AEM, make sure SQLCA (or whatever is the name of your transaction object in your app) is mapped to the data source you defined in AEM (e.g. "MAG").

Comment
There are no comments made yet.
Arthur Foux
Arthur Foux Accepted Answer Pending Moderation
  1. Thursday, 15 August 2019 18:28 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

The ODBC Administrator shown above is (32 bit) how do i activate the (64 bit) Administrator?

As I stated before, only 4 data sources displays in AEM instead of 16 or 20 in the (32 bit) ODBC Administrator.

Why is That?

Thank You for your immediate help.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 15 August 2019 19:35 PM UTC
I'm guessing because you did not install the 64-bit SQL Anywhere client. That never shipped with SQL Anywhere 7 and anyway SQL Anywhere 7 is not supported database (as Mike mentioned that's like 19 year old software). You should use a recent version of SQL Anywhere and during the installation process make sure you check both 32-bit and 64-bit client drivers. The PB IDE needs 32-bit and the PowerServer runtime needs 64-bit when you run on a 64-bit Windows OS. If you are on a 32-bit Windows OS then both the PB IDE and PowerServer runtime would just need the 32-bit driver.
  1. Helpful
Arthur Foux
  1. Arthur Foux
  2. Thursday, 15 August 2019 23:10 PM UTC
Thank You Armeen. I will use the instructions you provided and let You know when it is done.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Thursday, 15 August 2019 19:19 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

you are running version 7 of sql anywhere?  Not 17, but 7 that was released 19 years ago?

Comment
Arthur Foux
  1. Arthur Foux
  2. Thursday, 15 August 2019 23:05 PM UTC
Thank You Mike S. I was not aware it was that old. It worked with the previous versions of PB I was using.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 15 August 2019 20:32 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hi Arthur;

  The 64 bit ODBC Administrator can be found in the MS-Windows "Control Panel". When you add a System DSN from there, it will show you the SA driver option for that bitness.

HTH

Regards... Chris

Comment
Arthur Foux
  1. Arthur Foux
  2. Thursday, 15 August 2019 23:05 PM UTC


Thank You Chris.
  1. Helpful
There are no comments made yet.
Arthur Foux
Arthur Foux Accepted Answer Pending Moderation
  1. Friday, 16 August 2019 20:51 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 5

I am trying to migrate this 7.0.. database to 17

this is the error message i get.

Please tell me what to do to get this 7.0... to 17.

 

 

Comment
There are no comments made yet.
Arthur Foux
Arthur Foux Accepted Answer Pending Moderation
  1. Friday, 16 August 2019 20:53 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 6

I created a 17 database, I now need to get the tables, etc. from the 7.0... database to the 17 DB.

Thank you for your help.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 17 August 2019 00:45 AM UTC
Hi Arthur;

FYI: https://stackoverflow.com/questions/36895472/migrating-sybase-8-to-sybase-16



The same migration procedure should apply to SA7 to SA17.

HTH

Regards... Chris
  1. Helpful
There are no comments made yet.
Arthur Foux
Arthur Foux Accepted Answer Pending Moderation
  1. Friday, 16 August 2019 21:13 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 7

I tried closing the 7.0... server to see if 17 would find the file and do it's thing and this is what I got.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 16 August 2019 22:39 PM UTC
This looks purely like a SQL Anywhere migration issue... you may get better response posting in relevant SQL Anywhere forums. Since you are facing issues upgrading, I suggest you run a quick test using the 7.0. Use the native driver option in AEM instead of ODBC. You may find you can connect to it even though technically 7.0 is not a supported database because so old.
  1. Helpful
There are no comments made yet.
Arthur Foux
Arthur Foux Accepted Answer Pending Moderation
  1. Sunday, 18 August 2019 03:22 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 8

Is there a special directory for these dlls?

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Sunday, 18 August 2019 04:22 AM UTC
If this is a project you are doing for a company, you may want to have that company purchase a premium ticket and get this resolved that way. https://www.appeon.com/premium-support.html I'm afraid trying to resolve this particular issue through the Q&A will be futile.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.