where is the new access 2007 newsgroup?

[aaron.kempf]

since Access 2007 is a 'major change' then i assume that MS is going to
make a new newsgroup for it.

I mean; when VB.net 2002 came out; they decided to rename the 'main vb
newsgroup' as 'Microsoft.Publ ic.Dotnet.Langu ages.VB'

and now.. when people go to microsoft.publi c.vb they see 'vb as a dead
language'

so I nominate this newsgroup name for Access 2007

Microsoft.Publi c.Office.2007.A pplications.Acc ess

wouldn't that be great?
I mean; the Microsoft was is to assume that a longer group name makes
it MORE APPROPRIATE for a new version of Access..

above all, Microsoft needs to be consistent.

so who votes for
Microsoft.Publi c.Office.2007.A pplications.Acc ess

if they don't want to change the newsgroup name; then I ask that they
rename the vb group 'microsoft.publ ic.dotnet.langa uges.vb' to
microsoft.publi c.vb

I mean seriously here. They need to be consistent

Thanks

-Aaron

[dbahooker]

I agree.

we should either make a fucked up long ass newsgroup name for Access
2007 or we should UNDO the travesty for the microsoft.publi c.vb
newsgroup

consistency, microsoft

IM JUST DEAD FUCKING TIRED OF TYPING
'Microsoft.Publ ic.Dotnet.Langu ages.VB'

-Aaron

aa*********@gma il.com wrote:

since Access 2007 is a 'major change' then i assume that MS is going to
make a new newsgroup for it.

I mean; when VB.net 2002 came out; they decided to rename the 'main vb
newsgroup' as 'Microsoft.Publ ic.Dotnet.Langu ages.VB'

and now.. when people go to microsoft.publi c.vb they see 'vb as a dead
language'

so I nominate this newsgroup name for Access 2007

Microsoft.Publi c.Office.2007.A pplications.Acc ess

wouldn't that be great?
I mean; the Microsoft was is to assume that a longer group name makes
it MORE APPROPRIATE for a new version of Access..

above all, Microsoft needs to be consistent.

so who votes for
Microsoft.Publi c.Office.2007.A pplications.Acc ess

if they don't want to change the newsgroup name; then I ask that they
rename the vb group 'microsoft.publ ic.dotnet.langa uges.vb' to
microsoft.publi c.vb

I mean seriously here. They need to be consistent

Thanks

-Aaron

[The Grim Reaper]

Well stop bitching about it.. might save you some time in dictating.
Sorry, I mean typing.

I don't think I've EVER typed in that phrase.... :S

<db*******@hotm ail.comwrote in message
news:11******** **************@ 80g2000cwy.goog legroups.com...

>I agree.

we should either make a fucked up long ass newsgroup name for Access
2007 or we should UNDO the travesty for the microsoft.publi c.vb
newsgroup

consistency, microsoft

IM JUST DEAD FUCKING TIRED OF TYPING
'Microsoft.Publ ic.Dotnet.Langu ages.VB'

-Aaron

aa*********@gma il.com wrote:

>since Access 2007 is a 'major change' then i assume that MS is going to
make a new newsgroup for it.

I mean; when VB.net 2002 came out; they decided to rename the 'main vb
newsgroup' as 'Microsoft.Publ ic.Dotnet.Langu ages.VB'

and now.. when people go to microsoft.publi c.vb they see 'vb as a dead
language'

so I nominate this newsgroup name for Access 2007

Microsoft.Publ ic.Office.2007. Applications.Ac cess

wouldn't that be great?
I mean; the Microsoft was is to assume that a longer group name makes
it MORE APPROPRIATE for a new version of Access..

above all, Microsoft needs to be consistent.

so who votes for
Microsoft.Publ ic.Office.2007. Applications.Ac cess

if they don't want to change the newsgroup name; then I ask that they
rename the vb group 'microsoft.publ ic.dotnet.langa uges.vb' to
microsoft.publ ic.vb

I mean seriously here. They need to be consistent

Thanks

-Aaron

[Oenone]

db*******@hotma il.com wrote:

IM JUST DEAD FUCKING TIRED OF TYPING
'Microsoft.Publ ic.Dotnet.Langu ages.VB'

How many times a day do you have to type that? Apart from when posting to
the group saying how long the name is?

I'm not sure I've ever typed in the names of any of MS's newsgroups. I just
pick them from a list in my newsreader.

The name is a bit long, granted, but it seems like a reasonable name to me.
I don't think MS's newsgroup naming scheme is very consistent either but
don't really have a problem with it. As long as you can find the group you
want to post to (not usually very hard) then that's the important thing.
Having separate newsgroups for VB6 and VB.NET is a good thing, otherwise
half the traffic would be completely off topic, depending on your viewpoint.

There are more important things for MS to do than worry about public
newsgroup naming schemes IMO.

--

(O)enone

[aaron.kempf]

it's not a reasonable name

I can't find the group.. when I was first starting in VB.net (gag on
the name) I couldnt' find it for the longest time.. I finally posted in
microsoft.publi c.vb and someone told me that I needed to use this crazy
microsoft.publi c.dotnet.langua ges.vb

what a ridiculous name

it IS important

it IS a pain in the ass

it IS reflective of a major marketing problem... this is just ONE
SYMPTOM that Microsoft made VB 'take a fall' they threw the game

just like when the Chicago Black Sox threw their game; they lost a game
ON PURPOSE because they were betting on it.

I AM THAT FUCKING OUTRAGED.

and give me back www.microsoft.com/vb while you're at it.

yes; there are more important things for MS to worry about.

THE FUCKING FACT OF THE MATTER IS THAT THEY SHOULDNT HAVE CHANGED THIS
5 YEARS AGO.

TAKE YOUR VIRTUAL MAILBOXES AND SHOVE THEM UP YOUR ASS, MICROSOFT

Make microsoft.publi c.dotnet.langau ges.vb just a REDIRECT to
microsoft.publi c.vb

-Aaron

Oenone wrote:

db*******@hotma il.com wrote:

IM JUST DEAD FUCKING TIRED OF TYPING
'Microsoft.Publ ic.Dotnet.Langu ages.VB'

How many times a day do you have to type that? Apart from when posting to
the group saying how long the name is?

I'm not sure I've ever typed in the names of any of MS's newsgroups. I just
pick them from a list in my newsreader.

The name is a bit long, granted, but it seems like a reasonable name to me.
I don't think MS's newsgroup naming scheme is very consistent either but
don't really have a problem with it. As long as you can find the group you
want to post to (not usually very hard) then that's the important thing.
Having separate newsgroups for VB6 and VB.NET is a good thing, otherwise
half the traffic would be completely off topic, depending on your viewpoint.

There are more important things for MS to do than worry about public
newsgroup naming schemes IMO.

--

(O)enone

[mg]

Could you BE any more irrelevant?

aa*********@gma il.com wrote:

it's not a reasonable name

I can't find the group.. when I was first starting in VB.net (gag on
the name) I couldnt' find it for the longest time.. I finally posted in
microsoft.publi c.vb and someone told me that I needed to use this crazy
microsoft.publi c.dotnet.langua ges.vb

what a ridiculous name

it IS important

it IS a pain in the ass

it IS reflective of a major marketing problem... this is just ONE
SYMPTOM that Microsoft made VB 'take a fall' they threw the game

just like when the Chicago Black Sox threw their game; they lost a game
ON PURPOSE because they were betting on it.

I AM THAT FUCKING OUTRAGED.

and give me back www.microsoft.com/vb while you're at it.

yes; there are more important things for MS to worry about.

THE FUCKING FACT OF THE MATTER IS THAT THEY SHOULDNT HAVE CHANGED THIS
5 YEARS AGO.

TAKE YOUR VIRTUAL MAILBOXES AND SHOVE THEM UP YOUR ASS, MICROSOFT

Make microsoft.publi c.dotnet.langau ges.vb just a REDIRECT to
microsoft.publi c.vb

-Aaron

Oenone wrote:

db*******@hotma il.com wrote:

IM JUST DEAD FUCKING TIRED OF TYPING
'Microsoft.Publ ic.Dotnet.Langu ages.VB'

How many times a day do you have to type that? Apart from when posting to
the group saying how long the name is?

I'm not sure I've ever typed in the names of any of MS's newsgroups. I just
pick them from a list in my newsreader.

The name is a bit long, granted, but it seems like a reasonable name to me.
I don't think MS's newsgroup naming scheme is very consistent either but
don't really have a problem with it. As long as you can find the group you
want to post to (not usually very hard) then that's the important thing.
Having separate newsgroups for VB6 and VB.NET is a good thing, otherwise
half the traffic would be completely off topic, depending on your viewpoint.

There are more important things for MS to do than worry about public
newsgroup naming schemes IMO.

--

(O)enone

[C-Services Holland b.v.]

db*******@hotma il.com wrote:

I agree.

>
aa*********@gma il.com wrote:

>>since Access 2007 is a 'major change' then i assume that MS is going to

Wow, you're agreeing with yourself. Don't you think everyone knows
dbahooker and aaron.kempf are the same person? I guess I need to add a
few more aliases to my killfilter.

--
Rinze van Huizen
C-Services Holland b.v

[Homer J Simpson]

"mg" <bi*****@gmail. comwrote in message
news:11******** *************@n 67g2000cwd.goog legroups.com...

>
Could you BE any more irrelevant?

Don't repost the post - most everyone has plonked this idiot.

[aaron.kempf]

Homer;

I'm right.

WHY IS VB HAVE SUCH A RIDICULOUS NEWSGROUP NAME?

WHY DONT WE MAKE A NEW SIMILIAR ACCESS NEWSGROUP NAME?

-Aaron
Homer J Simpson wrote:

"mg" <bi*****@gmail. comwrote in message
news:11******** *************@n 67g2000cwd.goog legroups.com...

Could you BE any more irrelevant?

Don't repost the post - most everyone has plonked this idiot.

[aaron.kempf]

Homer;

I'm right.

WHY DOES VB HAVE SUCH A RIDICULOUS NEWSGROUP NAME?

WHY DONT WE MAKE A NEW SIMILIAR ACCESS NEWSGROUP NAME?

-Aaron
Homer J Simpson wrote:

"mg" <bi*****@gmail. comwrote in message
news:11******** *************@n 67g2000cwd.goog legroups.com...

Could you BE any more irrelevant?

Don't repost the post - most everyone has plonked this idiot.