Syntactically, we cannot use the “abort script” statement inside a “try … end try” block, which is a limitation (or may be for some logical reason) in Dex.

But most of the times, “abort script” is indeed a boon for most of the scenarios, where we need to skip the further processing of that particular script. How to overcome this?

We can simulate this “abort script” inside a “try … end try”. Check out the following code:

try
{regular code pieces}
if ProcessFurther = false then
throw EXCEPTION_ABORT_SCRIPT; {You can create this constant for reusability on your code with some integer value which you think is not used for any other System Exceptions}
else
{Proceed further}
end if;
catch
{Handle the Exceptions}
catch [EXCEPTION_ABORT_SCRIPT] {Your own Exception defined}
{Just do nothing. This is to simulate the “abort script” functionality.}
end try;

This is an easy way to simulate the “abort script” inside a “try … end try” block.

Other possibilities are most welcome.

Vaidy

Hi,

Can we display options while we right click on any resources in GP like in windows

Arun.

Hi,

Can we able to save image in tables & display it in forms and reports( retrieved from table where it saved)

Arun.

After the feature of adding a voice message welcoming us to Dynamics GP Application, here is one more different and pretty cool thing that we can do to our Dynamics GP. We can change the default Splash screen to the one which we would always like to see.

Read this article on David’s blog: Customize the Microsoft Dynamics GP Splash Screen.

Like it is mentioned, I did try with a completely different picture by renaming it to “splash.bmp” and copy it to the GP Application Folder. Wow, that’s pretty cool to see something different and something which I like the most whenever I log on to Dynamics GP.

It will be even more interesting to see some graphical image (Animated GIFs) support, but one can always desire more and more…

Vaidy

Well, one of the most annoying messages you could get in Dynamics GP Application.

How about seeing this message, instead of the Purchase Order Entry or Receivings Entry form, on a Monday morning, when there are piles of Receivings and POs to be entered on the System? Does not sound good, isn’t it?

Well, the only possible reason for this: This form would have been customized by some 3rd Party Application and the access would have been given to that version of the form. For instance (I always take this 3rd party product for explanations, not to offend it though), Project Accounting is the one which has customized almost all the forms in Purchasing module. There is each and every reason behind that, as the functionality and scope of Project Accounting lies very much inside Purchasing and each and every form of Purchasing module needed to be customized.

But then, the issue is, a Customer would have implemented Dynamics GP with Project Accounting (unintentionally) or a VAR without knowing the implications of PA towards the system would have installed GP with PA. This will automatically set the Security Settings for all the users to access Project Customized Purchasing forms. Now, when the Customer finally comes to know about this, and does not want Project Accounting on the environment, our VAR would have happily uninstalled the PA by “Changing the existing Instance of GP” option from Add/Remove Programs.

When the user try to open the Purchase Order Entry form, BANG, this message will pop up. And he will be out of his wits, to say the least. Calls here and there, blaming games start, situation more than panicky.

The access settings are mapped to Project Accounting based Purchasing Forms, but there is no PA dictionary at all on Client’s machine. How about it? And this is exactly what a client had faced and posted this as a query on MS Newsgroups. I was more willing to share this information to him and he was able to solve it.

The solution is simple. Open the Alternate Modified Forms/Reports, select the respective ID and change the access settings to the Microsoft Dynamics GP version of forms. That would do the trick.

And then came the input from David Musgrave. Setting access to default version for each and every form would prove more time consuming. Is there any other way to seamlessly do this? YES there is. Run the Reconcile on Security. This will remove all the stranded security access settings and change it to default settings.

Being an experienced developer in Customizations, I wanted to try this all by myself and removed some of the major Customizations from GP App. I then opened one of the affected GP Form and it threw this error. I then ran the Reconcile for Security, precisely Reconcile on “Security Assignment Alternate/Modified Operations”, those forms which are affected by the removed Customizations, were reset to Standard GP version. Wow, that’s quite nice to do this, because, we don’t have to worry about which are all the forms that are affected and need to be reset. All is done by just one click.

Now whenever someone ask this, I would say “Run Reconcile on Security”. Thanks to David for sharing this and I learned something new for me today.

Original Link of this post on MS Newsgroups: Cannot access this form because the dictionary containing it is not loaded.

Vaidy

Normally, while logging on to GP, we use to see the Login Screen, Company Selection Screen, then the Progress Bar showing stripes of Blues going on and on and on…

Why don’t we make it a more interesting atleast to see and hear? There is a way to do this. I was reading David’s articles, and came across this nice piece of VBA customization (original link: VBA – Welcome to Dynamics Example).

This not only enables a Welcome Message, but also opens up a lot of customization scope while logging on to Dynamics GP. We can certainly playaround to do more such interesting things, that spice up Dynamics GP.

For those, who had already gone thru’ the article, hope you guys have already gone miles with this customization example.

Vaidy

I had wondered for quite sometime, on seeing a message that says “This company is set up for testing. Please do not use this company for Live data processing.” (or something like that, not the exact message is provided here).

The reason for this message getting popped up: While creating the test company, the company name is entered with a “” (remove the double quotes) appended to the live company. For instance, if my Live Company is something like “Vaidy Inc.” then the test company which is created by moving the live data would be “Vaidy Inc. “””.

GP automatically recognizes this tag “” and considers this as a Test Company and pops this message whenever you log on to this company.

Quite interesting, isn’t it?

Vaidy

“The wait is over”. That’s the caption given by David on his blog, to signal the arrival of an Add-On which allows all VSTools Forms to be added to Standard GP Menus. Please check the below link:

Menus for VSTools Dynamics GP

It is available on PartnerSource and CustomerSource for download. It is official now. So all the developers can enjoy this feature, as most of the developers would have suffered for not being able to add their forms to GP Menus, which would have been a annoying disadvantage.

Let’s start rocking with this nice add-on.

Vaidy