"Today in History" project

I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

Conversion is not practical because ASP and Access are very different
technologies. You should be able to roughly replicate the design, but your
Access forms will have to be created from scratch. You might be able to
lift the odd function or bit of SQL, but even then the VB syntax used in
ASP.Net is so different to Access' VBA that very little, if anything, is
likely to be useable without some tweaking.

wrote in message
...
I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very different
technologies. You should be able to roughly replicate the design, but your
Access forms will have to be created from scratch. You might be able to
lift the odd function or bit of SQL, but even then the VB syntax used in
ASP.Net is so different to Access' VBA that very little, if anything, is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

Just a thought: if you've got a working ASP.Net application that you like,
then, depending on what Windows version you've got, you may be able to run
IIS and use the ASP application locally.

However, this being an Access newsgroup, if you want to pursue that further
you should do so in a more appropriate newsgroup.

Hope it may help.

wrote in message
...
Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very different
technologies. You should be able to roughly replicate the design, but
your
Access forms will have to be created from scratch. You might be able to
lift the odd function or bit of SQL, but even then the VB syntax used in
ASP.Net is so different to Access' VBA that very little, if anything, is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

Thanks for the thought, but no, I don't have any other ASP.Net
applications at all. Seems like starting from scratch is the way to
go. It'll be a learning curve for me, but then, that's what this is
all about in the first place!

Thanks again for your help. Much appreciated.


On Mon, 4 Jun 2007 07:54:26 +0100, "Baz"
wrote:

Just a thought: if you've got a working ASP.Net application that you like,
then, depending on what Windows version you've got, you may be able to run
IIS and use the ASP application locally.

However, this being an Access newsgroup, if you want to pursue that further
you should do so in a more appropriate newsgroup.

Hope it may help.

wrote in message
.. .
Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very different
technologies. You should be able to roughly replicate the design, but
your
Access forms will have to be created from scratch. You might be able to
lift the odd function or bit of SQL, but even then the VB syntax used in
ASP.Net is so different to Access' VBA that very little, if anything, is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

What about the one you mentioned in your first post? You even gave the
links for downloading it!

wrote in message
...
Thanks for the thought, but no, I don't have any other ASP.Net
applications at all. Seems like starting from scratch is the way to
go. It'll be a learning curve for me, but then, that's what this is
all about in the first place!

Thanks again for your help. Much appreciated.


On Mon, 4 Jun 2007 07:54:26 +0100, "Baz"
wrote:

Just a thought: if you've got a working ASP.Net application that you
like,
then, depending on what Windows version you've got, you may be able to
run
IIS and use the ASP application locally.

However, this being an Access newsgroup, if you want to pursue that
further
you should do so in a more appropriate newsgroup.

Hope it may help.

wrote in message
.. .
Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very different
technologies. You should be able to roughly replicate the design, but
your
Access forms will have to be created from scratch. You might be able
to
lift the odd function or bit of SQL, but even then the VB syntax used
in
ASP.Net is so different to Access' VBA that very little, if anything,
is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by
Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will
replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access
project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter
to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to
convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

Yes, but how do I get it to run? - I know nothing about ASP.net stuff.

On Tue, 5 Jun 2007 11:44:11 +0100, "Baz"
wrote:

What about the one you mentioned in your first post? You even gave the
links for downloading it!

wrote in message
.. .
Thanks for the thought, but no, I don't have any other ASP.Net
applications at all. Seems like starting from scratch is the way to
go. It'll be a learning curve for me, but then, that's what this is
all about in the first place!

Thanks again for your help. Much appreciated.


On Mon, 4 Jun 2007 07:54:26 +0100, "Baz"
wrote:

Just a thought: if you've got a working ASP.Net application that you
like,
then, depending on what Windows version you've got, you may be able to
run
IIS and use the ASP application locally.

However, this being an Access newsgroup, if you want to pursue that
further
you should do so in a more appropriate newsgroup.

Hope it may help.

wrote in message
.. .
Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very different
technologies. You should be able to roughly replicate the design, but
your
Access forms will have to be created from scratch. You might be able
to
lift the odd function or bit of SQL, but even then the VB syntax used
in
ASP.Net is so different to Access' VBA that very little, if anything,
is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by
Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This seems
like a good example to follow and once up and running, I will
replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to adapt
the sourcecode (freely available for download) into an Access
project,
but after a lot of reading over the last month or so, I still don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial matter
to
me (using the Wizard), but creating the required queries seems a lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I ask:

1. Would it be better to start the project from scratch or to
convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

As I said, this is an Access newsgroup. I'm sure there are ASP.Net
newsgroups which would help you.

wrote in message
...
Yes, but how do I get it to run? - I know nothing about ASP.net stuff.

On Tue, 5 Jun 2007 11:44:11 +0100, "Baz"
wrote:

What about the one you mentioned in your first post? You even gave the
links for downloading it!

wrote in message
.. .
Thanks for the thought, but no, I don't have any other ASP.Net
applications at all. Seems like starting from scratch is the way to
go. It'll be a learning curve for me, but then, that's what this is
all about in the first place!

Thanks again for your help. Much appreciated.


On Mon, 4 Jun 2007 07:54:26 +0100, "Baz"
wrote:

Just a thought: if you've got a working ASP.Net application that you
like,
then, depending on what Windows version you've got, you may be able to
run
IIS and use the ASP application locally.

However, this being an Access newsgroup, if you want to pursue that
further
you should do so in a more appropriate newsgroup.

Hope it may help.

wrote in message
.. .
Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very
different
technologies. You should be able to roughly replicate the design,
but
your
Access forms will have to be created from scratch. You might be
able
to
lift the odd function or bit of SQL, but even then the VB syntax
used
in
ASP.Net is so different to Access' VBA that very little, if
anything,
is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that
will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by
Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This
seems
like a good example to follow and once up and running, I will
replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to
adapt
the sourcecode (freely available for download) into an Access
project,
but after a lot of reading over the last month or so, I still
don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial
matter
to
me (using the Wizard), but creating the required queries seems a
lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I
ask:

1. Would it be better to start the project from scratch or to
convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

OK, thank you. I will have a look.

On Wed, 6 Jun 2007 09:53:11 +0100, "Baz"
wrote:

As I said, this is an Access newsgroup. I'm sure there are ASP.Net
newsgroups which would help you.

wrote in message
.. .
Yes, but how do I get it to run? - I know nothing about ASP.net stuff.

On Tue, 5 Jun 2007 11:44:11 +0100, "Baz"
wrote:

What about the one you mentioned in your first post? You even gave the
links for downloading it!

wrote in message
.. .
Thanks for the thought, but no, I don't have any other ASP.Net
applications at all. Seems like starting from scratch is the way to
go. It'll be a learning curve for me, but then, that's what this is
all about in the first place!

Thanks again for your help. Much appreciated.


On Mon, 4 Jun 2007 07:54:26 +0100, "Baz"
wrote:

Just a thought: if you've got a working ASP.Net application that you
like,
then, depending on what Windows version you've got, you may be able to
run
IIS and use the ASP application locally.

However, this being an Access newsgroup, if you want to pursue that
further
you should do so in a more appropriate newsgroup.

Hope it may help.

wrote in message
.. .
Thanks - that's what I needed to know.

On Sun, 3 Jun 2007 07:50:55 +0100, "Baz"
wrote:

Conversion is not practical because ASP and Access are very
different
technologies. You should be able to roughly replicate the design,
but
your
Access forms will have to be created from scratch. You might be
able
to
lift the odd function or bit of SQL, but even then the VB syntax
used
in
ASP.Net is so different to Access' VBA that very little, if
anything,
is
likely to be useable without some tweaking.

wrote in message
.. .
I would like to implement a "Today in History" application that
will
run at startup on a stand-alone machine.

Googling yielded "Today in History V.1.6 ASP .NET" developed by
Dexter
Zafra - see www.myasp-net.com and www.Ex-designz.net . This
seems
like a good example to follow and once up and running, I will
replace
the existing 'history' data with my own data (diary entries).

I initially thought it would be a relatively easy exercise to
adapt
the sourcecode (freely available for download) into an Access
project,
but after a lot of reading over the last month or so, I still
don't
know how or where to start the conversion.

Creating the database itself appears to be a fairly trivial
matter
to
me (using the Wizard), but creating the required queries seems a
lot
more daunting.

I'm a great believer in NOT having to reinvent the wheel, so I
ask:

1. Would it be better to start the project from scratch or to
convert
the above into an Access(2002) project?

2. If conversion is a practical proposition, where do I start?

Any pointers will be most appreciated. Thank you.

On reflection, I may have misunderstood what you said:

Just a thought: if you've got a working ASP.Net application that you like,
then, depending on what Windows version you've got, you may be able to run
IIS and use the ASP application locally.

What do you mean by "you may be able to run IIS" ?

Thanks