VBE capitalising "p" on new line
- Thread starter tuna
- Start date
- Local time
- Today, 22:31
- Joined
- Sep 12, 2006
- Messages
- 16,074
I might be wrong, i think it only capitalizes if its a new expression its not seen before, or if it matches an already declared variable
having said that, i see sometimes that when you enter a qualifier in a recordset, for instance sometimes you get
rst!myvariable, and other times you get
rst!MyVariable,
and I just dont understand why some get the treatment, and others dont.
having said that, i see sometimes that when you enter a qualifier in a recordset, for instance sometimes you get
rst!myvariable, and other times you get
rst!MyVariable,
and I just dont understand why some get the treatment, and others dont.
LPurvis
AWF VIP
- Local time
- Today, 22:31
- Joined
- Jun 16, 2008
- Messages
- 1,269
As wiklendt says, "VBE" = "Visual Basic Editor".
It was only referred to as such with the introduction of VBA AFAICR. (The editor then being a separate window).
I'm unclear on the 97 reference or what functionality was lost.
(I recall some lamenting the loss of the Expression builder in the VBE? Just wow - could not care less if I tried. Learning how to build expressions is such a fundamental Access skill that it is a good thing to lose IMO, maybe that's a bit cruel of me
.
Anyhoo... Intellisense (which is all the capitalisation is about) is the VBE's attempt to be helpful. Sometimes it's outstanding in that capacity, other times it's guessing wildly and annoyingly.
I'd agree that you'd probably have a variable, object or procedure named as such.
For it to capitalise immediately upon typing it implies that something else is afoot though. (Perhaps a Timer running causing a syntax check).
Generally if you ever get the phantom capitalisation - for example a built in object appears incorrectly such as, say, db.openrecordset - then just force it back by temporarily (very quickly) creating a proc of the name you'd expect.
Sub OpenRecordset()
End Sub
Then delete it.
Cheers.
It was only referred to as such with the introduction of VBA AFAICR. (The editor then being a separate window).
I'm unclear on the 97 reference or what functionality was lost.
(I recall some lamenting the loss of the Expression builder in the VBE? Just wow - could not care less if I tried. Learning how to build expressions is such a fundamental Access skill that it is a good thing to lose IMO, maybe that's a bit cruel of me
.Anyhoo... Intellisense (which is all the capitalisation is about) is the VBE's attempt to be helpful. Sometimes it's outstanding in that capacity, other times it's guessing wildly and annoyingly.
I'd agree that you'd probably have a variable, object or procedure named as such.
For it to capitalise immediately upon typing it implies that something else is afoot though. (Perhaps a Timer running causing a syntax check).
Generally if you ever get the phantom capitalisation - for example a built in object appears incorrectly such as, say, db.openrecordset - then just force it back by temporarily (very quickly) creating a proc of the name you'd expect.
Sub OpenRecordset()
End Sub
Then delete it.
Cheers.
DCrake
Remembered
- Local time
- Today, 22:31
- Joined
- Jun 8, 2005
- Messages
- 8,620
Moving from VBE to VBA caused the drop of one element that I found very freindly, which was the manipulation of the message box to included @Bold@ tags. This can now be replicated using a formatted message box as a UDF but I have found that it can sit on the task bar instead of on top of the form, especially if the form is a model popup.
I remember when migrating 97 apps to 2000 I had to trawl through all the code to remove the tags, really frustrating.
I remember when migrating 97 apps to 2000 I had to trawl through all the code to remove the tags, really frustrating.
LPurvis
AWF VIP
- Local time
- Today, 22:31
- Joined
- Jun 16, 2008
- Messages
- 1,269
Ah, the formatted messagebox huh.
Yeah, I suppose it could have been a pain. I'd used it somewhat judiciously myself thankfully.
FWIW though, I believe the workaround is still viable even in VBA 7.
(The workaround, of course, being the Eval execution as proposed by Michael Kaplan back in the day.)
But Access 97 did still use VBA (it was introduced in Office 95 as I recall, when the suite finally became more as one). As you'll no doubt recall, before that each app used its own flavour of Basic (AccessBasic, WordBasic etc).
The VBE is indeed more of an informal term for the IDE that's been used since (and hence more applicable to 2000 onwards when it was a distinct environment - spreading across all apps and even versions!)
It's hardly surprising that some folk find it hard to get into IT now with all the pre-existing TLAs.
Cheers.
Yeah, I suppose it could have been a pain. I'd used it somewhat judiciously myself thankfully.
FWIW though, I believe the workaround is still viable even in VBA 7.
(The workaround, of course, being the Eval execution as proposed by Michael Kaplan back in the day.)
But Access 97 did still use VBA (it was introduced in Office 95 as I recall, when the suite finally became more as one). As you'll no doubt recall, before that each app used its own flavour of Basic (AccessBasic, WordBasic etc).
The VBE is indeed more of an informal term for the IDE that's been used since (and hence more applicable to 2000 onwards when it was a distinct environment - spreading across all apps and even versions!)
It's hardly surprising that some folk find it hard to get into IT now with all the pre-existing TLAs.
Cheers.
ghudson
Registered User.
- Local time
- Today, 17:31
- Joined
- Jun 8, 2002
- Messages
- 6,193
I have had it happen to me on old databases that I inherited. A quick fix for changing capitals that are not behaving as expected if you want...
pTemp instead of Ptemp or PTemp is
Dim pTemp
Then remove the Dim pTemp after it fixes your problem.
pTemp instead of Ptemp or PTemp is
Dim pTemp
Then remove the Dim pTemp after it fixes your problem.
wiklendt
i recommend chocolate
- Local time
- Tomorrow, 09:31
- Joined
- Mar 10, 2008
- Messages
- 1,746
this just shows my age, but: how did people script VBA before VBE? there must have been a window of some sort available to input the code?
LPurvis
AWF VIP
- Local time
- Today, 22:31
- Joined
- Jun 16, 2008
- Messages
- 1,269
I guess, by contrast, I'm showing my age now... :-s
As I probably mentioned earlier, VBA was written in a code window part of the application. There was no shared IDE between the Office apps prior to 2000.
Not a radically different experience, except back in the 16 bit days - AccessBasic was somewhat different, as was the experience of writing it. (Not that I did much of that at all, but my first ever exposure to Access was version 2 - hence fond memories of it largely due to nostalia of the time - rather having performed any useful works in it :-s).
Cheers.
As I probably mentioned earlier, VBA was written in a code window part of the application. There was no shared IDE between the Office apps prior to 2000.
Not a radically different experience, except back in the 16 bit days - AccessBasic was somewhat different, as was the experience of writing it. (Not that I did much of that at all, but my first ever exposure to Access was version 2 - hence fond memories of it largely due to nostalia of the time - rather having performed any useful works in it :-s).
Cheers.
dfenton
AWF VIP
- Local time
- Today, 17:31
- Joined
- May 22, 2007
- Messages
- 469
Before the VBE, Access had its own code editor. The VBE was not much of an advance for Access users. To me, the motivation for making Access's VBA behave like the other VBA implementations in Office (e.g., defaulting to OMIT Option Explicit) had nothing to do with what was best for Access developers and everything to do with making the lives of MS's programmers easier.
