One of the things you will need to do if you haven't already done so is
increase your # Lock Table Entries on the data base.
From the progress explorer
Databases \ Mfgsys \Configurations \ Default Configuration
Then right click the Default configuration select properties
Select General and then increase the # Lock Table Entries. Mine is
currently set to 280000
You may also need to increase the Blocks DB as well (Not sure)
I believe you will need to restart the data base for the changes to take
effect.
Chris
_____
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of mmstark_scc
Sent: Wednesday, September 26, 2007 6:26 AM
To: vantage@yahoogroups.com
Subject: [Vantage] We want to turn on the G/L interface (6.1)
Hi! We do not currently have the G/L interface turned on in Vantage
and have never run a capture & post. Has anyone else out there been
through this? Tech support hasn't been much help and when we try to
run the capture & post routine in our test environment the process
stops with an error. Any guidance with this process would be
appreciated! Thanks!
[Non-text portions of this message have been removed]
increase your # Lock Table Entries on the data base.
From the progress explorer
Databases \ Mfgsys \Configurations \ Default Configuration
Then right click the Default configuration select properties
Select General and then increase the # Lock Table Entries. Mine is
currently set to 280000
You may also need to increase the Blocks DB as well (Not sure)
I believe you will need to restart the data base for the changes to take
effect.
Chris
_____
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of mmstark_scc
Sent: Wednesday, September 26, 2007 6:26 AM
To: vantage@yahoogroups.com
Subject: [Vantage] We want to turn on the G/L interface (6.1)
Hi! We do not currently have the G/L interface turned on in Vantage
and have never run a capture & post. Has anyone else out there been
through this? Tech support hasn't been much help and when we try to
run the capture & post routine in our test environment the process
stops with an error. Any guidance with this process would be
appreciated! Thanks!
[Non-text portions of this message have been removed]