Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Reports.dic issue

Status
Not open for further replies.

unclerico

IS-IT--Management
Jun 8, 2005
2,738
US
GP Version: 8.00g34
Dexterity: 8.00m076

We currently have GP installed on 8 computers and out of the 8 users there is only one person that makes changes to the Reports.dic file. Each morning a batch file runs to copy this person's Reports.dic file to a server share and then every other person runs a batch file to copy it down to their machines. I would think that everything would be gravy but at least once per day when someone tries to run a report a SQL error pops up (sorry I do not have the exact wording of the error, but I will post it when someone gets it again) and the only way to get this error to go away is to re run the download script manually. We also have a Windows 2003 terminal Server set up in a test environment and the same error is thrown when using this configuration but without the copy/download scripts. Any ideas as to what is going on?? Thanks a lot.
 
I think you might have a deployment issue. When are your users getting the updated file? In our scheme, we have a network share that is hosting our Reports/Forms. If a change is made to either file, the file is moved to a queue spot. At 3:00am a scheduled bat file moves the file to the share and removes it from the queue. The only person that is looking at a local Reports.dic is the person who changes the file and his Dynamics.set file reflects it. So just a recap:

Dev -> Queue -> .Bat Move/Delete -> Hosted on Share
 
Thanks for your response PCI...My users are getting the updated file each morning when they log into their machines through a download script set up in their startup folder, however, even if the reports.dic file didn't change the day before the file is still uploaded to the server share from the one person and then subsequently downloaded by everyone else with the download script. Our VAR has said that all of this copying has maybe corrupted the file but I don't buy it. When you say a queue spot, what exactly are you referring to?? Does it only do this if the file has been changed?? If so how do you make the determination that it has changed programmatically and not manually?? Do you make any changes to the "stock" Dynamics.set file?? I apologize for all of the questions as I have had a very quick and dirty 1 day training course on this beast. Thanks again.
 
Make a network share on any server, change the set file to reflect the new location, upload the file. Dynamics changes the reports.dic everytime it is accessed. The copying corrupting it, I doubt it. All users access the same file at the same time....

for instance:

from :C:eEnterprise/Forms.dic
to \\server\share\Forms.dic

in the set file.
 
The only person that wouldn't have this change in the set file is the reports developer, that way he would make the changes then push the file up to the network location on deployment.
 
PCI, you have been a great help thus far I really appreciate it. When accessing the Reports.dic file on a network share, does it create a lot of extra traffic on the network or is it minimal?
 
Minimal, I wouldn't worry one bit about that traffic. We have 4-5 of those dic/vba files located and shared thin-client style and we have monitored the traffic. It's really not a ton of traffic. Plus we have 35 users....
 
if you corrupt the dic you'll regret putting it on a share.

I would say that your user is probably launching GP before the batch file copying the modified report gets copied down. Check the syntax in your batch file. Maybe put it in as a policy instead and have it download before the user is logged in.



-----------
and they wonder why they call it Great Pains!

jaz
 
I agree, more chance for corruption on a network share with multiple users accessing the same dictionary. Network traffic is minimal though. Also, if you use a share you really shouldn't be making modifications while others users are in the system. This will cause corruption. Most of my clients do use a network share but they are not making changes to reports. Do a search on here...Dave M has posted a lot of reasons why he believes individual dictionaries are better.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top