Replication is really only intended for synchronizing *data* changes. It
doesn't handle significant form & report changes all that well. (It isn't
all that crazy about heavy changes to table structure either, if I remember
correctly, but that may have been just my experience).

In any case, you would still have a similar issue: your design master would
need to have been set up *before* it was distributed and data added by the
client.

HTH,

because the client already have a operational application deployed on site.
The user is looking for a way to send them a new updated appcation, but not
touch the data part. So, simply creating a new front end that will link to
the existing data file makes sense. The fact that the original appcation is
not split really don't matter, since you can send a new front end that will
link to their existing data file.

With replication, all kinds of new setup, and data files will have to be
created, and THEN placed on the clients computer, and further, to set that
up, either you have to travel to the clients location, or have the client
send you THEIR data while you setup replication. And, further, replication
assumes that you have some type of connection, which one may, or may not
have. Really, quite a complex process as compared to simply emailing a
client a new zipped mde file....

Further, as noted, replication is for replication of data, and trying to use
it for replication of software updates to an application is a disaster at
best, and at worst will not work for a mde file.....