[AccessD] Moderator Message

I wouldn't like to see AccessD watered down.  It should remain Access oriented and named 
accordingly otherwise we will cease to be a major source of Access expertise.

I'd suggest that we  need one other developer related list which would cover all the other 
technologies we are integrating Access with or using Access in (DBA-Dev ?). This would 
cover technologies such as virtualisation, web integration etc. as well as development 
environments (SQL Server/VB etc) and other Tech matters.

 I've just had a thought.  Some have been asking why the participation rate has gone down 
on Access-D, why we are not attracting new members or why it doesn't figure more 
prominently on search engines.  So I just had another look at 
http://www.databaseadvisors.com.   

You have to search really hard through the site before you even find a reference to Access.

You certainly can't tell from the entrance page that our main interest is Access solutions or 
that we are a source for solving Access problems.  The first thing a  casual visitor sees is 
advertisements for:

A Sharepoint book
A .Net project
Microsoft Training for Windows 7
Conficker Test
An article on Office Addins
Microsoft's Azure platform
....


and just to rub it in, here's the Description from the headers on each page: 
	<meta name="description" content="Database Advisors was founded in order to 
provide developers, using primarily .Net, VB, SQL and C# a place to discuss what we do, 
why we do it, what works and what doesn't." />

No mention of Access!

Maybe it's time for a redesign?

-- 
Stuart


On 8 Aug 2009 at 12:28, Max Wanadoo wrote:

> Sorry Shamil,
> 
> I must totally disagree with this.  This is a top-down approach from a.

> systems analyst.
> 
> But we are not talking here about a software solution but a "People"
> solution.
> 
> IMO you have too many, far too many, divisions.  Most of my IT stuff crosses
> these borders time and time again.
> 
> I would say we need only 3 lists.
> 
> 1. DBA-IT (your AccessD, DBA-VB, DBA-IT below, anything MS related really) -
> these all intermingle for me time and time again.
> 
> 2. DBBA-Tech - Anything computer/development related which does not fall
> under 1.
> 
> 3. DBA-OT - Anything - General chat.
> 
> The Friday OT relaxation can be maintained/stopped - I have no preference.
> 
> I would not like to see a plethora of Lists because they do not reflect real
> life development.
> I am not doing .net etc but love reading about it (osmosis learning) and if
> a subject comes up which I am not at all interested in, I just click Delete.
> 
> I am currently working on a project which involves Access, VBScript and .HTA
> (HTML) within the one project.  I would like to post this to just No.1 above
> and not bit-wise across three lists.
> 
> 
> Well, there we go.  My 2 Roubles <g>
> 
> Max
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
> Salakhetdinov
> Sent: 08 August 2009 11:22
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Moderator Message
> 
> Hi All,
> 
> Here is my proposal on AccessD discussions rules:
> 
> AccessD - MS Access/VBA only
> 
> dba-VB  - VB.NET/C#/.NET only
> 
> dba-IT  - MS Access/Office/VBA/MS SQL/C#/VB.NET/.NET Framework
>           /MS Windows System/Hardware etc. - practical, final 
>           result oriented, everyday software development
>           business discussions...
> 
> dba-IT-OT - IT development related stuff - any, including 
>           discussions of conceptual/computer science stuff...
> 
> dba-IT-ChitChat - Friday Humor, Max vs. JC (and similar) jokes e-mail
> ping-pong etc.
> 
> dba-OT - everything.
>