-
Eric Ellis
- InfoMaker
- Sunday, 30 June 2024 11:07 PM UTC
Greetings -
I've been using Infomaker off and on for 20ish years, but I primarily write SQL code directly in SSMS because I find it easier. I'm not here to argue that point, I just offer it as a background understanding for this question.
I have a new client who needs have their development done primarily in Infomaker because their users are not comfortable with raw code. Fine - I don't need to proselytize one way or the other. However, I'm running up against some issues in Infomaker (Version 2022 build 1892) that are throwing me for a loop, and I'd appreciate some advice on how to address them.
I should also we're working in an environment where there's a im.ini file being pushed to all users, including myself. Here's the contents of that file:
[PB]
WebLink1=&Community Q&&A,https://community.appeon.com/
WebLink2=&Online Product Manuals,https://www.appeon.com/documents
WebLink3=&Technical Support,https://www.appeon.com/developers/get-help.html
ToolbarText=0
ToolbarTips=1
TestIni=PowerStudio
PbCrashFlag=1
OpenSelection=2
RunSelection=1
NewSelection=2
NewDefaults=0 11 1 0
NewDimensions=553, 393
SystemOptionsPage=0
[Database]
AutoQuote=1
Columns=8
NoCatalog=No
ReadOnly=0
ShowIndexKeys=1
ShowReflnt=1
StayConnected=1
TableDir=1
TableListCache=1800
TerminatorCharacter=;
TableSpace=*
HideComments=1
ShowRefInt=1
[Data Window]
Preview_RetainData=1
PreviewRetrieve=0
Stored_Procedure_Build=1
Report_Governor_Cross=0
Report_Governor_Outerjoin=0
Report_Governor_Distinct=0
OverlayLineWidth=1
ruler=1
outline_objects=1
[Window]
Default3D=1
DefaultDataSource=1
GridOn=0
GridShow=1
GridX=8
GridY=8
Status=0
[SQL Painter]
HideFlags=CDL
[Application]
WorkingDir=D:\...
TempLib=C:\...
DefLib=D:\...
StyleLib=D:\...\IMSupportStyles.pbl;D:\...\IMSupportProduct.pbl;
[Debug]
Platform=x86
[Library]
IncludeFiles=0Issue One: Unavailable "Convert to Syntax" in the Query designer. I go to File -> New -> Database -> Query and start a new query. I'm presented with the "Select Tables" dialog box; I choose the tables and views I want to work with. I'm landed in the familiar workspace, with Table_Layout above, the Sort/Where/Group/Having/Compute/Syntax tabs below. (I'll state here that my prior experience hasn't been in the Query designer, it's been almost exclusively in the Tabular report where I've used the SQL Select option to define the report data.) But I have no option to Convert to Syntax - is this intended? If not, how would i alter this behavior? This wouldn't be critical, except for Issue Two...
Issue Two: Retrieving and using database objects from a schema other than dbo. Ok, this may be self-inflicted wounds, but with this client, I and the client's DBAs agreed we'd use a separate schema for the database objects we'd create than the "dbo" schema that their primary ERP vendor is using. It was done only as a convenience - the separate schema made it clear which objects we had created. When I open the "Select Tables" dialog box, I do see these objects in the list (though not their schema prefix), but when I attempt to use the query including these objects, there's an error box showing that the objects can't be found. Because I can't convert the query to syntax, I can't add the schema to the object name; when I do the same process in the query designer of a tabular report, I can convert the query to syntax and add the schema name to the objects, and everything works fine. Do I have any option to fix this issue?
I appreciate any assistance anyone can offer!
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.