Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
1
Nomads / Re: Stretchable Embedded Panel
« on: November 07, 2022, 10:02:47 AM »
Hi Ron,
I tried creating an embedded panel with a rectangle shape control 2 lines high. It did not work correctly when the embedded panel height was defined as 3 - but did work when the embedded panel was made higher (14 high). Only the rectangle is embedded - but the height/width ratio is used when trying to compute how to stretch the controls.
Hope this helps
I tried creating an embedded panel with a rectangle shape control 2 lines high. It did not work correctly when the embedded panel height was defined as 3 - but did work when the embedded panel was made higher (14 high). Only the rectangle is embedded - but the height/width ratio is used when trying to compute how to stretch the controls.
Hope this helps
2
Language / Re: Excel, .COM, and OneDrive
« on: June 02, 2022, 09:10:01 AM »
James,
I tried this again when I had book1.xlsx already opened in Excel and the x'CreateWorkbook("",1) did fail.
Checking x'ERROR'Message$ returns the message Can not access 'Book1.xlsx'.
Susan
I tried this again when I had book1.xlsx already opened in Excel and the x'CreateWorkbook("",1) did fail.
Checking x'ERROR'Message$ returns the message Can not access 'Book1.xlsx'.
Susan
3
Language / Re: Excel, .COM, and OneDrive
« on: May 30, 2022, 09:19:10 AM »
James,
Perhaps this is unrelated to the update ...
Is it possible that the default Book1.xlsx file already exits and was opened or in use elsewhere? The CreateWorkbook method attempts to add a workbook and then tries to save it with the supplied path. If no path is supplied, it will try to save it with the default path and may fail. It may be easier to supply a path name - but you can also call the Create Workbook method with a second parameter - a flag telling the object to always overwrite the existing file (in this case Book1.xlsx).
return_value=x'CreateWorkbook("",1)
Perhaps this is unrelated to the update ...
Is it possible that the default Book1.xlsx file already exits and was opened or in use elsewhere? The CreateWorkbook method attempts to add a workbook and then tries to save it with the supplied path. If no path is supplied, it will try to save it with the default path and may fail. It may be easier to supply a path name - but you can also call the Create Workbook method with a second parameter - a flag telling the object to always overwrite the existing file (in this case Book1.xlsx).
return_value=x'CreateWorkbook("",1)
4
Language / Re: Excel, .COM, and OneDrive
« on: May 27, 2022, 03:18:56 PM »
James,
I just tried it here and it still seems to work for me. Did Excel itself get updated? What version of Excel are you running?
Susan Cryderman
PxPlus Technologies Ltd.
I just tried it here and it still seems to work for me. Did Excel itself get updated? What version of Excel are you running?
Susan Cryderman
PxPlus Technologies Ltd.
5
Programming / Re: Opening Excel Workbook while open in *obj/excel
« on: November 17, 2021, 11:36:48 AM »
James,
I'm not sure I understand the issue. If I open an existing Excel workbook using the OpenWorkbook method in the *obj/excel.pvc object and then try to open it directly in PxPlus with an OPEN command - I get an error 0 message - the same as I would get if I try to open it on PxPlus while it is opened in Excel itself.
I'm not sure I understand the issue. If I open an existing Excel workbook using the OpenWorkbook method in the *obj/excel.pvc object and then try to open it directly in PxPlus with an OPEN command - I get an error 0 message - the same as I would get if I try to open it on PxPlus while it is opened in Excel itself.
6
Nomads / Re: FM generator issues
« on: August 03, 2021, 09:10:24 AM »
Hi Stéphane,
Thanks for letting us know about these issues. We will look into solutions for the next update.
Thanks for letting us know about these issues. We will look into solutions for the next update.
7
Programming / Re: Dragging cells within table
« on: August 31, 2020, 10:06:37 AM »
Cedric,
One think I forgot to mention ...
You also need to disable the 'MultiSelect property on your grid control in order for the system to know the difference between selecting multiple cells and dragging a cell.
One think I forgot to mention ...
You also need to disable the 'MultiSelect property on your grid control in order for the system to know the difference between selecting multiple cells and dragging a cell.
8
Programming / Re: Dragging cells within table
« on: August 28, 2020, 08:25:02 AM »
Hello Cedric,
Yes - you can setup drag and drop from a grid control (GRID_1.CTL) to the same grid control. If you then enter some PERFORM logic, this logic can do something like;
r1=GRID_1.CTL'draggedrow,c1=GRID_1.CTL'draggedColno
r2=GRID_1.CTL'droppedOnRow,c2=GRID_1.CTL'droppedOnColno
Once you have these drag and drop rows and columns - you can then use them to retrieve the current values (GRID_1.CTL'value$) and other properties of the cells as needed.
Yes - you can setup drag and drop from a grid control (GRID_1.CTL) to the same grid control. If you then enter some PERFORM logic, this logic can do something like;
r1=GRID_1.CTL'draggedrow,c1=GRID_1.CTL'draggedColno
r2=GRID_1.CTL'droppedOnRow,c2=GRID_1.CTL'droppedOnColno
Once you have these drag and drop rows and columns - you can then use them to retrieve the current values (GRID_1.CTL'value$) and other properties of the cells as needed.
9
Nomads / Re: File Maint with Main window data fields and Folder
« on: November 27, 2019, 12:02:34 PM »
The legacy File Maintenance programs (prior to version 2019) sometimes hid code and settings in the library file itself. This was one of the reasons we re-designed File Maintenance in the 2019 release.
It might help to generate the panels again with a different name and then try replacing some of the controls on your existing panel (maybe the key) with the newer version.
It might help to generate the panels again with a different name and then try replacing some of the controls on your existing panel (maybe the key) with the newer version.
10
Nomads / Re: File Maint with Main window data fields and Folder
« on: November 27, 2019, 09:30:18 AM »
It's hard to say exactly what might be happening since you are using a custom F/M program. In our standard program, the FIELDS group should become enabled if the _ENABLE_FLG variable is set in the FIND_REC method. There is a bit of logic to determine this - based on the number of key fields to be entered etc.
Is there more than one key field on the panel? Were any of the tweaks made to the panels affecting key fields?
Is there more than one key field on the panel? Were any of the tweaks made to the panels affecting key fields?
11
Nomads / Re: File Maint with Main window data fields and Folder
« on: November 26, 2019, 04:46:13 PM »
James,
A couple of questions ...
Were the original panels generated as File Maintenance panels and then edited in NOMADS? If so, which folder tab (first, second, third) was removed?
A couple of questions ...
Were the original panels generated as File Maintenance panels and then edited in NOMADS? If so, which folder tab (first, second, third) was removed?
12
Programming / Re: Writing CSV files
« on: July 03, 2019, 08:48:18 AM »
Hello Mike,
You should be able to instantiate the object as follows to indicate that the Excel is to be run locally on the workstation;
x=new("[lcl]*obj/excel")
However - the path$ arguments cannot include [lcl] or [wdx] tags.
You should be able to instantiate the object as follows to indicate that the Excel is to be run locally on the workstation;
x=new("[lcl]*obj/excel")
However - the path$ arguments cannot include [lcl] or [wdx] tags.
13
Programming / Re: *obj/Excel - When Dropped Excel Closes
« on: June 12, 2019, 02:11:58 PM »
Josh,
Thanks for your explanation. We will look into adding some sort of property to the next release which can be set if you wish excel (or word) to remain open when the object is dropped.
In the meantime - you could try creating your own excel object which inherits our object. This object will contain only the definition of the EXCEL property. Our object is coded with a SET ERR on the EXCEL property - but if your object is not, setting the EXCEL property to 0 might accomplish what you wish.
create an object (for the purposes of this example I have named it excel2.pvc):
! *obj/excel2 - MS Excel object which keeps Excel open
!
DEF CLASS "*obj/excel2"
!
LIKE "*obj/excel"
!
! Properties
PROPERTY EXCEL OBJECT ! Handle to main Excel object
!
END DEF
and then, in your code:
x=new("*obj/excel2")
x'openworkbook("someworkbook")
x'visible=1
excel=0
drop object x
Hope this helps!
Thanks for your explanation. We will look into adding some sort of property to the next release which can be set if you wish excel (or word) to remain open when the object is dropped.
In the meantime - you could try creating your own excel object which inherits our object. This object will contain only the definition of the EXCEL property. Our object is coded with a SET ERR on the EXCEL property - but if your object is not, setting the EXCEL property to 0 might accomplish what you wish.
create an object (for the purposes of this example I have named it excel2.pvc):
! *obj/excel2 - MS Excel object which keeps Excel open
!
DEF CLASS "*obj/excel2"
!
LIKE "*obj/excel"
!
! Properties
PROPERTY EXCEL OBJECT ! Handle to main Excel object
!
END DEF
and then, in your code:
x=new("*obj/excel2")
x'openworkbook("someworkbook")
x'visible=1
excel=0
drop object x
Hope this helps!
14
Nomads / Re: ERR=10 *nomads /pvx/lib/*winproc - Line 230
« on: May 06, 2019, 08:55:01 AM »
It looks like line 230 of *winproc is dealing with the Prefix value from Library Defaults. I'd check that the library default Prefix setting for the screen library where you have created your query is correct.
15
Nomads / Re: AutoCompName in Grid
« on: March 29, 2019, 03:16:54 PM »
In case anyone else is having the same issue - the fix is a one line change to either the *winold/control.grd program (if using NOMADS+ or Folder Style) or the *win/proppresets program if using Property Sheets.
If you load either program in an editor - you should see that line 163 defines a variable called prop_both$ that is a long list of properties.
The AUTOCOMPNAME property needs to be added to this list. It does not really matter where - but they are currently alphabetical so we can add it as follows;
prop_both$="ALIGN,AUTOCOMPNAME,AUTOVALUE, ...
(don't forget the comma afterward).
This should allow both the column and row values to be specified.
If you load either program in an editor - you should see that line 163 defines a variable called prop_both$ that is a long list of properties.
The AUTOCOMPNAME property needs to be added to this list. It does not really matter where - but they are currently alphabetical so we can add it as follows;
prop_both$="ALIGN,AUTOCOMPNAME,AUTOVALUE, ...
(don't forget the comma afterward).
This should allow both the column and row values to be specified.
Pages: [1] 2