sql server msde: I am building an application with a SQL Server 2005 Express backend. I
would like to create a secondary instance the database on another
server that will serve as a fail-over in case the primary server goes
down (there is only the Express version of SQL Server in this picture).
I see that replication in SQL Server Express only works as a
subscriber and not a publisher. Can anyone suggest a method that I can
ensure that both instances of the database propagate data between them
when they are both available? The app is written in VB.Net.

Thx,
Marcus

Marcus,
with no log-shipping, database mirroring or replication publishing, your
choices are limited. However, log-shipping might not be available out of the
box but you could create your own scripts to perform it. You won't have sql
agent, but still could use windows scheduler to initiate your 'jobs'.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)