Guest
Guest
B7332 sp 11.1, NT, SQL server 7.0
I have been told that you can create a full package installation CD to do
client installs instead of pushing them through the network. I have also
been told to use Product Packaging to do this. But, to me it seems that
Product Packaging is for updates only and seems a bit complex at my CNC
stage (6 months). Is it poosible to do full package CD's and is it easy?
The problem, I had deployed multiple custom reports that were working fine.
Until recently a couple of users were running a custom TB variance report
that showed double the amount for the month of May while other users had no
problems. All packages built correctly and were deployed to the two
workstations in question. On the first machine I tried to check out the
report locally and got a spec error. I then re-installed the full package
and re-tried the check out and got the same error. I then removed the JDE
installation via WINDOWS NT ADD/REMOVE programs and deleted the rest of the
B7 directory. After re-installing I was able to check in and/or run the
report successfully. With the second user I had the same error when checking
out. This time I logged out, turned on debugging and was going to re-do the
check out hoping to get the error logged. But, I checked out successfully
and I was able to run the report with no problems. It has nothing to do with
security as I was using the users ID. Does this ring a bell with anyone?
Thanks,
Crawford Winter
Transamerica Life Canada
I have been told that you can create a full package installation CD to do
client installs instead of pushing them through the network. I have also
been told to use Product Packaging to do this. But, to me it seems that
Product Packaging is for updates only and seems a bit complex at my CNC
stage (6 months). Is it poosible to do full package CD's and is it easy?
The problem, I had deployed multiple custom reports that were working fine.
Until recently a couple of users were running a custom TB variance report
that showed double the amount for the month of May while other users had no
problems. All packages built correctly and were deployed to the two
workstations in question. On the first machine I tried to check out the
report locally and got a spec error. I then re-installed the full package
and re-tried the check out and got the same error. I then removed the JDE
installation via WINDOWS NT ADD/REMOVE programs and deleted the rest of the
B7 directory. After re-installing I was able to check in and/or run the
report successfully. With the second user I had the same error when checking
out. This time I logged out, turned on debugging and was going to re-do the
check out hoping to get the error logged. But, I checked out successfully
and I was able to run the report with no problems. It has nothing to do with
security as I was using the users ID. Does this ring a bell with anyone?
Thanks,
Crawford Winter
Transamerica Life Canada