815
I am trying to see whether I should use Visual Studio Tools or Modifier With VB to make changes to GP screens (add new text fields, save them in the database, etc)? One of my concerns is the Visual Studio tools are relatively new (but free) while Modifier with VB has been around for a while but is expensive.
Does anyone have insight as to which tool would be better to use or are they both equally useful?
Any feedback would be helpful.
Thanks
Ladd Sustar
.
*This post is locked for comments
I think I'll respectfully disagree with the previous post. I think there's a time and place for each of the tools. But if you wish to modify the appearance of GP windows, as your post mentions, your only options are Modifier/VBA or Dexterity. The Visual Studio Tools could move things around on a window via code, but cannot add new content to a window.
In the plus category for Modifier/VBA is that it is significantly easier to learn than Dexterity, especially if you've used VBA in another environment. However, the previous poster did correctly stated that there are some tricky things with Mod/VBA. But I wouldn't throw the baby out with the bath water. It's the only tool available that will allow you to modify 3rd party windows, such as windows in any ISV product or in any non-core dictionary (like project accounting, manufacturing, etc.)
I have a couple of tips for you in using Modifier/VBA. First of all, you can aquire the GP User's connection to the database. This will allow you to read/write data to the SQL Server without storing your own credentials. If you're a GP customer or partner, you should be able to view this link:
Also, when doing record management in Mod/VBA, many windows contain the fields "Save Record" and "Display Existing Record". These fields are invisible, usually below the window area. With Modifier, you can make them visible and drag them onto the window surface. Once they are displayed, you can "Add fields to Visual Basic", and then make them invisible and drag them back to where they were. Now that they are added to your VBA project, you can add code to the "DisplayExistingRecord_AfterUserChanged" event, and then the "SaveRecord_AfterUserChanged". Alternatively, you can add code to the "SaveRecord_BeforeUserChanged" event and even stop the save by setting the optional byref parameter "Cancel" = True.
Good luck.
Ron DraganowskiSt Paul, Minnesota
rdrag@ottechnologies.com
http://www.ottechnologies.com
Here is my experience, and this is purely my view based on my experience:
Rule 1 - stay away from vba, I had very very bad experiences with vba
Rule 2 - if you want develop in GP, meaning modify windows, do automations etc, use Dexterity
Rule 3 - if you want to do fancy data exports etc use .net or c sharp
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,253
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
