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

Resolved Custom Database Providers

  1. How-to
0
Votes
Undo
  1. Jeff Wilkinson
    Jeff Wilkinson
  2. PowerServer
  3. Friday, 12 May 2023 14:31 PM UTC

In a PowerServer 2022 project when setting up a new database, there are a set of predefined Providers like Oracle, SQL Server, MySQL and a few others.  However, on the server (and my local development machine) we have an ODBC Connection for a cTree driver that we use in PowerBuilder apps.

How would I add this "Provider" as a usable option?  This is pretty critical to our deployments using PB 2022 and PS 2022.

Thanks!

Jeff

Error opening 32-bit DLL in a 64-bit PB app
Run PS but failed with error
Responses (3)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 20 May 2023 15:28 PM UTC
  2. PowerServer
  3. # 1

Hi Jeff, Only supported databases can be used for PowerServer.  I know this is quite different than client/server where through ODBC you can connect to basically anything.  Anyway, CTree definitely is not a supported database and we have no plans to do so on the roadmap: https://www.appeon.com/developers/roadmap

 

Comment
There are no comments made yet.
Jeff Wilkinson
Jeff Wilkinson Accepted Answer Pending Moderation
  1. Friday, 12 May 2023 15:01 PM UTC
  2. PowerServer
  3. # 2

That is really too bad as I use the ODBC driver for this specific db in C# programs as well and things work great there.   Thanks for the reply.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 12 May 2023 15:17 PM UTC
The key here is .NET vs .NET Core. If cTREE though is planning a .Net Core driver that they can then deliver inside a NuGet package - then Appeon could consider this for PS. Of course, if that is the case - then please submit a cTree support ticket as an enhancement request.



However, the other alternative I could suggest (whicj I have used at various customer sites) would be to use SQLAnyWhere DBMS's "Proxy Table" feature. In SA, you can create a "PT" (virtual table) that in turn then SA redirects the DML to the appropriate DBMS using whatever driver (in your case ODBC). So your App still makes "what it thinks" are cTREE table requests but these go to SA instead first. Then SA, performs the actual cTREE requests & returns a standard ODBC result set back to your PB / PC / PS Apps. Thus, they are "none the wiser" about whatever DBMS, non-SQL, file access method, etc is actually being traversed (including updates). Food for thought. HTH

Regards ... Chris
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 12 May 2023 15:18 PM UTC
FYI: https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbusage/proxy-omni-using.html

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 12 May 2023 14:48 PM UTC
  2. PowerServer
  3. # 3

Hi Jeff;

  Unfortunately because PowerServer DB drivers are specific to C# .NET Core environment, they must be a driver that is a) supplied by the DBMS vendor specifically and b) supports C# .Net core runtime. Thus currently, only the PS "DB Providers" currently listed meet this criteria. So if your DBMS is not listed in the PS Provider section then it's not supported.

   Please contact the cTree software vendor to find out of they are planning to supply such a DB driver in the future.

Regards .. Chris

Comment
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.