F
frank knuckles
Aaron,
In stead of disturbing the atmosphere on this newsgroup and putting a
tremendous amount of time in making useless messages I would like to ask you
the following.
Why don't you use your time and energy in a more constructive way? Read on.
Your answer to almost every question is SQL server. I don't know anything
about SQL server. Let's assume that (sometimes) there is some thruth in your
advice about SQL server. Why don't you help us to explore that?
I recently tried to install SQL-server Express and after an hour I was
dazzled by all the downloads and manuals I had to read to even get started
with it. The learning curve is/seems really steep. Evertyhing is simple once
you know how to do it.
So my question is: Could you write a step by step instruction for us on how
to get started with SQL server? You could take an example of an Access
database of which you want to keep the frontend in Access but move the
backend to SQL server.
That way we might be able to benefit from your enthusiasm.
FK
In stead of disturbing the atmosphere on this newsgroup and putting a
tremendous amount of time in making useless messages I would like to ask you
the following.
Why don't you use your time and energy in a more constructive way? Read on.
Your answer to almost every question is SQL server. I don't know anything
about SQL server. Let's assume that (sometimes) there is some thruth in your
advice about SQL server. Why don't you help us to explore that?
I recently tried to install SQL-server Express and after an hour I was
dazzled by all the downloads and manuals I had to read to even get started
with it. The learning curve is/seems really steep. Evertyhing is simple once
you know how to do it.
So my question is: Could you write a step by step instruction for us on how
to get started with SQL server? You could take an example of an Access
database of which you want to keep the frontend in Access but move the
backend to SQL server.
That way we might be able to benefit from your enthusiasm.
FK