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

Resolved PB No Longer showing Database Columns

  1. Issue
0
Votes
Undo
  1. Dominick Levi
    Dominick Levi
  2. PowerBuilder
  3. Friday, 1 September 2017 13:13 PM UTC

Recently our database server was upgraded and although PowerBuilder runs fine, when I click design, data source for a datawindow I get the following error.

"Table "csd_currentenrollmentcount" has no columns; possible invalid table format.
Please check to see if the active DB Profile is correct.
Do you want to continue in graphics mode?"
Graphics mode does not display anything as well.

I checked that the DB Profile is correct, even created a new one thinking the other may have been corrupt. Still get the error.

Also created a new ODBC connection.
Does anything need to be done to the .pbw to correct this issue?

I am using PowerBuilder 12.6 and MS SQLServer 12

Thank you in advance

  1. ASE
About AutoCompile (pbc170).
SOLVED: How to integrate SVN with PowerBuilder
Responses (3)
Matthew Balent
Matthew Balent Accepted Answer Pending Moderation
  1. Friday, 1 September 2017 13:44 PM UTC
  2. PowerBuilder
  3. # 1

Have you tried creating a new DB connection in PowerBuilder since the DB upgrade?

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 1 September 2017 13:48 PM UTC
  2. PowerBuilder
  3. # 2

Hi Dominick;

  The PB IDE gets information about data entities by using a DESCRIBE DML function (among others). In order to do this, your DB login needs to have these type of DML permissions. This might be your problem.

  I have personally upgraded from SS2008 to 2012 and now to 2016 this past 12 months and my PB App DWO's have not had this issue. I have used the newer SS's with PB 12.1, 12.5.1, 12.6 and now PB 2017 - successively migrating my DWO's across each PB version. Again, no issues like you have described. However, I always login with full DBO privileges.

Food for thought.

Regards .. Chris

 

Comment
Dominick Levi
  1. Dominick Levi
  2. Monday, 11 September 2017 18:45 PM UTC
Hi Chris,



Thank you for your feedback. I have admin privileges associated with the database. It's just strange that we have a server upgrade twice and both times I got that error. Datawindow objects that were created before the upgrade would give me that error. Any new datawindow objects could be viewed without a problem until a server upgrade took place then they too would give me the same message.



Thank you again for your reply

  1. Helpful
Dominick Levi
  1. Dominick Levi
  2. Tuesday, 12 September 2017 14:53 PM UTC
Hi Chris,



Thank you for your feedback. I have admin privileges associated with the database. It's just strange that we have a server upgrade twice and both times I got that error. Datawindow objects that were created before the upgrade would give me that error. Any new datawindow objects could be viewed without a problem until a server upgrade took place then they too would give me the same message.



Thank you again for your reply

  1. Helpful
There are no comments made yet.
Dominick Levi
Dominick Levi Accepted Answer Pending Moderation
  1. Wednesday, 13 September 2017 16:56 PM UTC
  2. PowerBuilder
  3. # 3

Hi Chris, Thank you for your feedback. I have admin privileges associated with the database. It's just strange that we have a server upgrade twice and both times I got that error. Datawindow objects that were created before the upgrade would give me that error. Any new datawindow objects could be viewed without a problem until a server upgrade took place then they too would give me the same message. Thank you again for your reply

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.