DataBase - Extender vs Modifier
Asked By barbola
26-Jan-10 02:29 PM
Our organization can probably benefit from both of these products but if we
had to choose one, what would other users recommend?
We have limited development skills/resources but a couple of people have VBA
knowledge (incl me). The system admin (me) also has an excellent knowledge of
the GP tables and SQL.
I know I will have to evaluate based on need, and will be putting that
together in my recommendation. We have the need for both additional fields
for Cards and Transactions.
We also have the need for better lookups, additional windows, and windows
for other data we track such as transport loads which eventually get invoiced
out of our transp division to other divisions and external customers, and
tracking transactions from a company-owned fuel pump.
What are some other uses you have been able to use these products for,
individually and together?
VBA
(1)
Blogster
(1)
Extender
(1)
Musgrave
(1)
Day
(1)
Windows
(1)
Transp
(1)
Incl
(1)
Mariano Gomez replied to barbola
Take a look at the conference material David Musgrave and I put together for
our presentation at last November's Microsoft Dynamics GP Technical
Conference. The material is part of my article "Microsoft Dynamics GP
Technical Conference 2009 - Day 1" at
http://dynamicsgpblogster.blogspot.com/2009/11/microsoft-dynamics-gp-technical_11.html
I am sure it will help you with answering this question, which by the way,
is a bit extensive to cover in this forum.
Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com
barbola replied to Mariano Gomez
Awesome! Thank you! That is alot of information. I think from what I found on
Extender, we will have to evaluate the two and see which one meets our needs
and is a good fit for our level of expertise.
Thanks,
Barb
Outlook (1) I should note that I am using the data macro to call a VBA function (by setting a local macro variable to the result of the function call). So this is not for the web, I did not see a problem with calling a VBA function (and various places I have seen online mentioned workarounds for calling VBA from a data macro). But, again, while it works when I insert a record in note? In it I added that I was using the AfterInsert macro to run some VBA code (by setting a local variable to the result of a function call). Maybe that maybe that is the problem Yes, in this case, you need a copy of the VBA in the front end. (for testing you can place it in both - since if you happen to open the back end table directly, then the VBA code is ALSO required since the front end might not even be open and the talk to that may be sitting on your computer. So when the trigger fires, that VBA code will be required. So, the VBA needs to exist in the front end if that all you opened. However, if you
reusable for more than one client. So we now develop to a office standard (and VBA). Our next and software for the cloud will be built to the sharepoint standard (at an application to 100% on the desktops without never having any server system anywhere. The day I received some server space, was the day I published that application to the web. The only reason why there was problems because shape to be compatible for upload? But not with native Access forms. Not with standard VBA. This means it may be *similar* to Access (and thus very easy for us to web, and one for local. In fact you can even execute an open form from VBA and openform works fine if you feed it a web form name. as mentioned, you can have a mix of VBA forms, and web only forms in the same application. When you publish the application, those help you trace the interconnections between all the macros, the same way you can with VBA. This is my biggest concern about all of this, that by going to macros, you need a date field, but just a year column would suffice anyway (the month and day become not that important for dates earlier than 1900 anyway in most applications). If buy
VBA vs Macros DataBase Let me preface this by saying it is a sincere question. I Using Access 2010 I note that help tells us to use macros in preference to VBA for web apps and for greater security. Also a VBA to macro converter is provided but not the other way around. Why so down on VBA? Once upon a time it was considered that for any serious development VBA was preferred to macros because it had a) error trapping (where untrapped errors would crash runtime installation of Access) and b) greater power and flexibility. Are these two advantages of VBA over macros still true with 2010? Other than for web apps (which I am not doing) should I change to macros or stick with VBA? When I took up Access I learned VBA and only did macros when it was the only way for certain operations. Other than
big of post do you want? Perhaps the big news is the new version of VBA, or what we call VBA 7. This new version of VBA now has a true pointer data type called longPtr. We also get a 64 bit the term JET, but I really talking about ACE). Note that this new version of VBA of course is also runs on the 32 bit version of windows. -> Database triggers and WEB features in access 2010. I think it is pretty well split. Just the other day I was telling someone that I was absolutely thrilled enjoyed that Access 2007 did not features are are more oriented towards developers (such as a new data Pointer type in VBA - we never had a data pointer type in VBA. Too bad we did not, as the switch to 64 bits would have been seamless all well, when we jump to 128 bit computers, Access and VBA will be ready because we now have a true pointer data type). Other features will
correct term. I am talking about Dbs to which you set a reference in the VBA references section. Secondly apologies for sort-of reposting this question, but I drew blanks last the Tools-> References section. As far as I know it is not possible to use VBA to compact and repair. I cannot find any way of removing the reference from the I have a reference set to "Menu.Accde" in the Tools-> References section of the VBA editor, then I uncheck the reference, Menu.AccDe still shows up in the project explorer Only those functions = 93can not be found = 94. But you can refresh the reference through VBA, by looping through the References. Especially when you have more than one reference that must the ambiguities from the programmer = 92s side, but that Access could refresh the reference for VBA, but failed to do that for (I assume) Jet Expression Service. After an Access.References except the one it was originally compiled with. The entire process can be automated using VBA and automation, so it is not as tedious as it sounds. Steve What old "Switchboard code." I also use late binding for everything but the basie three Access references (Access, VBA, DAO). Extra code? Not so much, but it is harder to code when you do is useful if there is a conflict with other libraries. . . just like you can call VBA.MsgBox() or simply MsgBox(). Of course, you know all that. The Help file DOES state