1. Saroj Mungtaweepongsa
  2. PowerBuilder
  3. Tuesday, 4 July 2017 15:53 PM UTC

My system is Window 10 64bit and daabase is MS SQL Server Express 2014.

ODBC Database connection :

Try 8 difference ways of odbc connection (2 Drivers / 32 & 64 bit odbc / User DSN / System DSN). All of these connect to the same database.

 

 

 

 

 

 

 

 

 

 

PowerServer Toolkit Configuration

1) DB Type Profiles for MSSQLServer using Native Interface. [CONNECTION SUCCEEDED]

 

 

 

 

 

 

 

 

 

 

2) DB Type Profiles for MSSQLServer using ODBC Interface. There are 6 ODBC files shown in dropdown list and all of these 6 ODBC connection succeeded. The missing 2 ODBC are 64bit System DSN for both ODBC & Native Driver.

 

 

 

 

 

 

 

 

 

 

 

3) Data Source Profiles Configuration (Using Native Driver). It take a long time trying to connect and returned CONNECTION FAILED.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4) Data Source Profiles Configuration (Using ODBC Driver). The missing 2 ODBC from 2) appear here, but no the other 6 ODBC. Confused?? It difference from DB Type Profiles Tab. But these 2 ODBC CONNECT SUCCEEDED and very fast. And I noticed that there are only 64bit System DSN ODBC listed here.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

5) But, PowerBuilder IDE Database Profiles Setup could not select all the 64bit System DSN ODBC.

 

 

 

 

 

 

 

 

 

 

 

And, if I used System DSN 64bit ODBC in SQLCA.DBParm then CONNECTION FAILED. And the mobile app also return CONNECTION FAILED.

 

 

 

 

 

 

f I change to another ODBC, the PowerBuilder IDE can succeeded connecting , but the mobile app still return CONNECTION FAILED.

 

Appeon Support Team Accepted Answer Pending Moderation
  1. Wednesday, 5 July 2017 06:31 AM UTC
  2. PowerBuilder
  3. # 1

Hi Saroj,

#1- For the Data Source Profiles Configuration (Using Native Driver) connection failed issue, please try the solution stated in the article below to resolve it.  

http://support.appeon.com/index.php?/Knowledgebase/Article/View/48/0/cannot-connect-to-the-sql-server

#2- For the ODBC Database connection failed issue:

On the one hand, if the PB application is 32 bit, then it can only connect to 32-bit ODBC with IDE;

On the other hand, if  you have the 64-bit Power Server installed, then it can only connect to 64-bit ODBC.

Therefore, if you compile the program under 32 bit then you just need to use 32-bit ODBC but don’t need to run the 64-bit. However, it seems that you are using the same name for the 32/64-bit ODBC driver on the basis of the screenshot you provided, which indicates that it can select 32 or 64 bit ODBC driver accordingly. That’s the main cause of this issue.

Additionally, for the Powerserver, Appeon doesn't support to use the ODBC Driver to connect the SQL Server, and it is recommended to use the SQL Server Native Driver to resolve this kind of issue.

Moreover, if you want to use the Appeon mobile app, then please configure the transaction object to data source mapping to avoid this kind of issue. For more details on how to do the configuration please refer to the help documentation at: https://www.appeon.com/support/documents/appeon_online_help/2016/server_configuration_guide_for_net/ch03s05.html

 

Thanks,

Appeon Support Team

Comment
  1. Saroj Mungtaweepongsa
  2. Wednesday, 5 July 2017 07:53 AM UTC
Hi  Appeon Support Team,



 



I followed your instructions and use the SQL Server Native Driver. Right now, my Android Smart Phone can success connecting to database on my PC.



 



Thank you so much,



Saroj



 

  1. Helpful
  1. Appeon Support Team
  2. Friday, 7 July 2017 06:18 AM UTC
Hi Saroj,



Glad to hear that! 



Regards



Appeon Support Team



 

  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.