- ProIV Resource Centre
- → Viewing Profile: Posts: CSuarezdelReal
Community Stats
- Group Members
- Active Posts 91
- Profile Views 6,385
- Member Title Advanced
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
Previous Fields
-
Year Started ProIV
1995
-
Highest ProIV Version Used
4.6
-
Company Working For
Amdocs / AT&T
-
Companies Worked For
AlliedSignal, Honeywell, Cummins, Delphi Automotive, Tyco Valves and Controls, Hitachi Global Storage Technologies, Solectron/Flextronics, Grupo Mega
0
Neutral
User Tools
Friends
CSuarezdelReal hasn't added any friends yet.
Latest Visitors
Posts I've Made
In Topic: #VAR = SQL COUNT(*)
27 June 2006 - 02:20 PM
I recall SQL DYNAMIC does not work on v4.6.
In Topic: #VAR = SQL COUNT(*)
23 June 2006 - 01:59 PM
I would use Martin's approach, but looks like you do not want to mess with files. When you say Bob's advice does not work, do you mean you get zero, an error ...or what?; have you tried to use :$VAR instead?.
In Topic: Can you read a trace file?
02 June 2006 - 03:07 PM
May I suggest getting a fresh backup of all your functions before you execute such reggens?.I have not modified any programs. However, it appears my predecessor changed the function GLOVIA, but never regenned it. As part of another process GLOVIA had me regen all functions. So, whatever change he made has now been genned. I will have to ask Glovia for the original function to compare and see what he did.
Assuming the DRIVE file is the fault, I would recommend COPYING the GLOVIA function as it is today, and troubleshoot the COPY (any development or testing environment to do so?). You can then remove the line where the DRIVE file is being processed from the GLOVIA function. I understand GLOVIA (the ERP) would run OK anyway.
When you find what goes wrong, just apply the changes to the live GLOVIA function. That should save you some unnecessary crashes.
Could you post what is the structure of file DRIVE (both, SL and ORACLE)?.
In Topic: COMBOBOX Gray
25 May 2006 - 02:13 PM
scminter,
The change of color to gray means that button is no longer active; do you want to keep it active in the page loop, or want just to keep the color for aesthetic purposes?
The change of color to gray means that button is no longer active; do you want to keep it active in the page loop, or want just to keep the color for aesthetic purposes?
In Topic: How often do you visit ProivRC
14 February 2006 - 02:21 PM
Rob,
I would say people may come here daily, but most of them do not respond to the poll the very day it is published. For other polls I have responded even a few weeks after it appeared.
:-)
I would say people may come here daily, but most of them do not respond to the poll the very day it is published. For other polls I have responded even a few weeks after it appeared.
:-)
- ProIV Resource Centre
- → Viewing Profile: Posts: CSuarezdelReal
- Privacy Policy