Access is slower programming than Excel. No Intellisense

  • Thread starter Thread starter Webtechie
  • Start date Start date
You'll find that although Excel may seem easier, that it isn't neccessarily
more powerful. The decision to develop something in Excel or Access *must* be
based on a full understanding of the capabilities of each as well as any
limitations inherent in either.
Click to expand...

"You can drive nails with a crescent wrench but that doesn't make it a
hammer".

For that matter you could probably, in a pinch, loosen a hex bolt with the
claws of a hammer.

It helps to have a well stocked toolkit, either in your computer or in the
garage!
 
As a veteran VBA programmer in Excel, you would notice that when you type the
space after DoCmd.OpenForm, intellisense quite clearly notifies you that the
only required argument is for the form name. And the variable stLinkCriteria
(which is optional) is never set in the example you show, so you can delete
that line right out. And then you should know also that you can hardcode the
form name rather than storing it in the stDocName variable, so then you can
get rid of those two lines. Which leaves you with one line:

DoCmd.OpenForm "frmFindFiles"


For someone who's developed a number of major applications using VBA in
excel, you don't seem to be putting much effort into this in Access. Looking
at a function and Intellisense's argument list is pretty basic to any VBA,
regardless of the host application. So the only thing to learn here is to
use the DoCmd.OpenForm method rather an MyForm.Show

Use your imagination a little and try to read between the lines when you
pull something out of a book (or the help files)...

--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)
 
Is it a IDE design issue or users just not understanding the concept of
Object Models and necessary differences between the various OM's of Office?
 
Just like me taking 6 months to do something in ASP.NET that I could do in
less than 6 weeks in Access...even factoring in not working on it 8 hours a
day / 5 days a week.
 
I'm still curious about the two questions that I asked...

1) Why do you need to grab the value in a control on one form and use it in
code in another?

2) What features in Excel are you using?

....and a third...

3) Can you describe the application that you're building?
 
Back
Top