Forms.dic question

(0) Share

Report

Posted on by Community Member

Hi,

While preparing for the upgrade to Dynamics Gp2010 [from GP 10], I was reviewing the Dynanmics.set file.

In it I see the following entry:

\\our_servername\reports\FORMS.DIC

however, when I navigate to that path the forms.dic doesn't exist.

1) How do I find the correct forms.dic file?

2) How do I move that to

\\our_servername\reports\

Thanks.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

You may not have any custom forms. Are you licensed for Modifier? FORMS.DIC is for modified screens and REPORTS.DIC is for your modified reports. If have not modified any forms you will not have a FORMS.DIC. Do any of your screens have a period(.) before the screen title? That would indicate a modified form.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

1) what is modifier?

2) I dont know about the period (.) - since I am a IT person - not an accountant who uses this software.

Any way to check this?

thx

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Modifier allows you to modify your screens. If you are using a modified form you would see a period before the form name in the upper left-hand corner of the form. My guess is NO and you have no worries about the forms.dic file.

Was this reply helpful? Yes No
Victoria Yudin 22,769 on at

Like (0)

Report

As Richard said, you may simply not have any modified forms (aka windows) and thus will have no FORMS.DIC file - that file is only created if needed. To double check, when in the GP application you can go to Tools | Customize | Customization Maintenance - if under Type there is nothing that says Modified Form, then you do not have any.

My 2 cents - if you do not have any, why have the install pointing to a file share instead of locally? Every time someone launches GP, it has to go out to the file chase and check for the file. All other things being equal, it is usually faster to check a local resource.

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

Victoria is 100% correct as normal. :) If there is no file there is no need to point to a shared location. You are only adding time for the login process as GP needs to go out across the network to attempt to load that dictionary.

Was this reply helpful? Yes No
Victoria Yudin 22,769 on at

Like (0)

Report

Thanks Jonathan, that made my day! :-)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have a question, if there is no modification to the forms.dic, and it still points to the c:\program files\Microsoft Dynamics\GP, and there is not a forms.dic in this folder, what do you do about the error you are receiving when you launch GP for the first time in a new environment? Can you delete the entry in the dynamics.set file? We are trying to set up a test environment and are running into these types of problems. We do have a modified form in the frms949.dic. and have that dictionary.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

What is the error message you are receiving? If your DYNAMCIS.SET file points to a FORMS.DIC that is empty you should not be receiving any error messages. Make sure that none of your workstations have a FORMS.DIC file that do have modified forms in it. It is possible that your security knows about them from other workstations. Also, make sure whatever path you are pointing to is valid.

Was this reply helpful? Yes No
Suggested answer

Redbeard 12,931 on at

Like (0)

Report

Sam,

I felt compelled to suggest an answer to this one, despite the excellent replies to this post. Richard, Victoria and Jonathan are all on the same page, and from what I can tell, it's definitely the right page - no one marked a suggested answer, so there is no way to confirm the solution.

You likely do not have a Form (GP Window) customization. Please check the pointer in the Dynamics.Set file on all workstations, to ensure this is indeed the case. Check each pointer location for a Forms.dic file. Checking customization maintenance on one workstation will be insufficient, because various workstations can have completely separate configurations.

The likely reason the Dynamics.Set file points to a shared location on a server, is your parnter/predecessor were being thorough about the their configuration settings, ensuring any customization created using Modifier would be available to any GP user.

Once you've validated you have no customization, set the pointer in the Dynamics.set file to the default location in each workstation would save overhead caused by GP checking the server location for an absent file every time it starts.

Was this reply helpful? Yes No