New front end releases and report redesigns

[Bill Reed via AccessMonster.com]

I was just considering placing reports and forms in a kind of "back end"
repository so that I could update them and not have to redistribute the front
end.

As usual, I've inherited a pretty messy ad hoc mdb. It's kind of like fixing
a bicycle while someone's riding it. I am constantly making design changes to
the back end to get it up to snuff, and that necessitates frequent
distributions of redesigned front ends (and there are 4 varieties). It would
be great if there were some way to "link" the front end to reports and forms
in a "back end" so that I wouldn't have to constantly update and distribute
front ends.

Am I dreaming or is there some way of accomplishing this? Of course I don't
mean to actually link them continuously, but to link the front end
periodically to a repository of forms and reports in order to replace old
versions with new ones.

Bill

 

[Rick Brandt]

I was just considering placing reports and forms in a kind of "back end"
repository so that I could update them and not have to redistribute the front
end.

As usual, I've inherited a pretty messy ad hoc mdb. It's kind of like fixing
a bicycle while someone's riding it. I am constantly making design changes to
the back end to get it up to snuff, and that necessitates frequent
distributions of redesigned front ends (and there are 4 varieties). It would
be great if there were some way to "link" the front end to reports and forms
in a "back end" so that I wouldn't have to constantly update and distribute
front ends.

Am I dreaming or is there some way of accomplishing this? Of course I don't
mean to actually link them continuously, but to link the front end
periodically to a repository of forms and reports in order to replace old
versions with new ones.

Could be done I suppose, but there are a number of ways to automatically
distribute entire front ends that would be a LOT simpler, faster, and less
problematic.