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

Resolved Infomaker Form Crashing

  1. Issue
0
Votes
Undo
  1. Keeley Stalnaker
    Keeley Stalnaker
  2. InfoMaker
  3. Tuesday, 27 April 2021 21:54 PM UTC

Hi;

 

 

I recently modified an Infomaker form (using 2019 r2) to connect to a SQL Server database rather than Oracle. The form is used so people can add new users to roles. I am assuming it was made in the one-to-many type because it is supposed to return a list of users in a specified role, and allow people to add a new username to that role in our database. All the SQL Server columns and tables are the same as the old version, and the update functionality is working as expected on the SQL Server table.

Basically, you can update that column just fine in my new SQL Server version of the form, but it's not displaying what's already there even though the column is on the screen. I tried deleting and adding back the column but no dice. Screenshot is attached.

When I go to Design>Master/Detail Relationship, Infomaker crashes, and also crashes if I try in IM2017. I figured I would just make an entirely new form, but Infomaker also crashes when trying to create a new form. It just says "loading tables" and freezes. frown

Attachments (1)
Form.JPG Form.JPG
  1. InfoMaker
  2. SQL Server
Infomaker License
Custom Function - Return pbl name, datawindow name...
Responses (3)
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 29 April 2021 13:03 PM UTC
  2. InfoMaker
  3. # 1

The other thing to check is the user RIGHTS in the new database.

Have you tested the SQL of the DW in a stand-alone environment? For Oracle that would be Toad or SQL+.

Comment
There are no comments made yet.
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Thursday, 29 April 2021 06:07 AM UTC
  2. InfoMaker
  3. # 2

Hi Keeley,

 

I built a small test case but can’t reproduce it on our side.

From your screenshot, it seems your form is not complicated.

I suggest you try to create a new PBL in your IM 2019 R2 and recreate this Form window in this new PBL to see if the same issue exists.

Besides, does the issue also exist if you perform the same steps on other machines?

 

If the issue is still reproducible, we recommend reporting this problem to our ticket system:https://www.appeon.com/standardsupport/newbug so it can be properly received and tracked. 

Please also provide a sample test case (with PBL) when you submit it to the ticket system. Thanks in advance.

Regards,

Comment
Keeley Stalnaker
  1. Keeley Stalnaker
  2. Friday, 7 May 2021 19:02 PM UTC
Thanks for the reply!

Yes, the form is just to add new user names to a table that contains only usernames and roles. When the form is run, the user is prompted for the role, which displays in the header. The detail section should display the users in that role, but that column is showing up blank.

However, when the user clicks the "new" button and adds a user, this is successful and the database is immediately updated with a new row. There are reports in the same PBL that are all properly showing data when run.



I tried making a new PBL and making a new form, but Infomaker freezes then crashes when trying to load tables. Infomaker also crashes when trying to view tables in the database painter.

I also have some Powerbuilder apps using this connection and they are working fine. But, trying to open the database painter in Powerbuilder also causes freeze then crash.



I also tried on another machine and same thing.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 27 April 2021 22:54 PM UTC
  2. InfoMaker
  3. # 3

Hi Keeley;

 It sounds like a possible DB client connection issue. How is IM setup to connect to SS. That is, which DB Profile type is your IM IDE using?

Regards ... Chris

Comment
Keeley Stalnaker
  1. Keeley Stalnaker
  2. Wednesday, 28 April 2021 21:08 PM UTC
Hi Chris;

I think that just may be. I am using SNC SQL Native Client. This is the exported profile:



[DBMS_PROFILES]

Profiles=My_Profile_Name





[Profile My_Profile_Name]

DBMS=SNC SQL Native Client(OLE DB)

Database=

UserId=

DatabasePassword=whatever

LogId=our_master_user

LogPassword=whatever

ServerName=Our_Server_Name

DBParm=Provider='SQLNCLI11',Database='our_db_name',CommitOnDisconnect='No'

Lock=

Prompt=FALSE

AutoCommit=FALSE

NewLogic=EAS



Thanks!
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 29 April 2021 14:10 PM UTC
Hi Keeley;

These settings look standard except for the "NewLogic=EAS". I have no idea what that is.

BTW: What version of SS are you using and do you have the equivalent version of the SS DB Client installed?

FYI: I am not having any issues with IM2017 / 2019 with my SS2019 DBMS.

Regards ... Chris

  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.