Error while importing Package File 1

[GPUser05]

I exported a package file of modified report and try to save as different name and import it so I can modify the report. While importing I am getting error "unable to open customizations Dictionary." Any thoughts is highly appreciated.

Thanks,

 

[klewis10367]

Are there users logged into the system?

 

[GPUser05]

Thanks a lot for quick reply. You saved my day. I was doing it first time and did not know this. Thanks again. I am new to this forum but find it very helpful.

 

[winthropdc]

Just some comments:

I highly recommend against using shared customisation dictionaries (except on terminal server/citrix). I much prefer using local custom dictionaries and use a process to synchronise workstations with a central update are upon log in.

This has the following benefits.

1) Never being locked out of report writer or modifier because others users are in the system.

2) Reduces chances of corruption the custom dictionaries.

3) Improves performance as base resources and customised resources are read from local drive rather than network.

4) Allows customisations to be fully tested before being deployed.

5) VBA has to be stored locally in .VBA files anyway.

------------------------------

FYI: Great Plains v8.0 has a bug which can corrupt VBA packages exported using Customisation Maintenance. This is fixed in Service Pack 2.


David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer
MBS Support - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[stef315]

I like network ones for other reasons:

1. Many times don't have vba.
2. Ensured backup of dictionaries on server.
3. Changes made globally instead of having to roll out to all workstations.
4. Reduces confusion over different versions of the same report. Ever try to figure out which version to keep?
5. Can reconcile security restrictions from any workstation without fear.
6. When you do an upgrade, all you have to do is verify everyone is using the shared dictionaries instead of local ones--instead of stressing that you are going to miss some modified report one user had on their local dictionary only. So, you only upgrade one Reports or Forms dictionary.

I don't think the network traffic is an issue in most cases. They are easier to corrupt which means you have to make a copy before you do anything that touches it (modifications, service packs, new module installs).

Modifications can be done from a Development launch file that points to a local Dev Reports dicitonary and then imported when ready. Many of my larger clients have a complete development environment with seperate installs, servers, etc. due to Dexterity customization changes to already modified windows.

Anyway, just my thoughts. There are obviously pros and cons to both methods.

 

[winthropdc]

All of those benefits are still available in a synchronised system.

All upgrades and changes get posted into the update area and automatically distributed to every workstation on next login without having to visit the machine.

This includes all executables, application dictionaries AND custom dictionaries.

David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer
MBS Support - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.