Front End and Back End General Questions

[Tony Toews [MVP]]

The utility appears to copy everything down from the server directory. But
it only creates one Icon for what is specifeed in the ini. So I would need a
seperate ini for each FE. It would make sense to put each master FE in it's
own sub folder then, wouldn't it? And if I do that, I might as well keep them
within the specific group as far as access rights are concerned, rather than
herd all the front ends to one place. That way, a user can try to run all
the ONIs but will only be successful in the one's for which her has rights to
the FE. Sound like I'm finally getting it?

Correct. StartMDB would give the user some message such as file not
found or such and wouldn't be able to copy down the FE.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews [MVP]]

I guess I missed the original "man-in-the-middle" concept, and took it as
more of a management utility. You can add some text to your description . .
. .but I was asking too many questions before I tired it out, too.

I changed a few things in a paragraph describing how it worked but
that was about it.

And since different FEs (not copies of this one, different ones all
together) are sprinkled around the network, creating different INIs pointing
to those locations keeps even the FEs getting copies to an un authorized
computer. I like it!

Glad to hear it.

Then, when I started looking INI documentation, I started getting real
excited about the future of this. Great job. I will be deploying it to other
desktops (as MDE files BTW) within the next week or so.

Even better.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[G-Man]

OK. What am I doing now!

When I try running the StartMDB on other workstations, I get your Null
Command Line sent to Utility. If you are using a shortcut . . . . Please
contact your coputer department for support."

Um . . . that would be me. And I can;t get me to answer any of my calls!

What have I missed. I found your FAQ indicating that you has made this error
more understandable. I'm usre you have. But it's me you're dealing with! I'm
sure I was so excited that I could get it to work for me that I missed
something in the "other workstations" part of things.

Thanks so much.

 

[Tony Toews [MVP]]

OK. What am I doing now!

When I try running the StartMDB on other workstations, I get your Null
Command Line sent to Utility. If you are using a shortcut . . . . Please
contact your coputer department for support."

Um . . . that would be me. And I can;t get me to answer any of my calls!

What have I missed. I found your FAQ indicating that you has made this error
more understandable. I'm usre you have. But it's me you're dealing with! I'm
sure I was so excited that I could get it to work for me that I missed
something in the "other workstations" part of things.

This is a bit of tough concept to explain. And I know I need to have
a better explanation here.

For other users to start using the utility for the first time you need
to create a shortcut, or a .cmd/.bat file, on the server for the users
to click on. You can use the shortcut the Auto FE Updater previously
created on your system by copying it to the server.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[G-Man]

OK. I know how to create a Batch file. But I still do not understand what I
need to do. I pute orgional StartMDE on a network drive and ran it there.
From the INU file, it new to create folder on my desktop and where to pull
master FE.

But what shortcut do I put on the users computer? Do I put a copy of the
same shortcut the program created on MY machine? I told the INI file to
create the icon on my desktop called "roduction Database" THIS is what I
need to copy yo other computers? So I am the only one (or me and other
"masters") unning the StartMDE. From that point on, it's just copying icons
to desktops?

 

[Tony Toews [MVP]]

But what shortcut do I put on the users computer? Do I put a copy of the
same shortcut the program created on MY machine? I told the INI file to
create the icon on my desktop called "roduction Database" THIS is what I
need to copy yo other computers? So I am the only one (or me and other
"masters") unning the StartMDE. From that point on, it's just copying icons
to desktops?

Not quite. You put a copy of this shortcut on the server in an
appropriate folder. Then the user just clicks on that shortcut which
starts the process. But the user only needs to do that once. The
first time the user runs that shortcut it will then create the
shortcut in the location you've specified on their computer such as
the Desktop. After that they just click on the shortcut.

One client has four different databases in the folders inside the
Database folder. So in that folder he put the four shortcuts.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[G-Man]

Got it! I created copies of all the FEs and put them in folders parallel to
the current productions FEs. I then put copies of the current production FEs
in these folders. Users go right on using the "old" FEs while I run tests on
the new setup. It's running perfect. As I make changes, I see the database
re-copied to the local machine. I lock the FEs, unlock them, initiate the
routine from other desktops. It's all working great.

Currently, however, all the FEs are MDBs. I started MDE conversion, but I'm
getting smoked with compliation errors. (agan, not my work here . . .someone
elses). Where I can, I'm fixing. But in some forms I can compile fine, but
the converter still says compilation errors exist. So, I'm going to live
with FEs that are MDBs for now, while I weed some more things out. But I am
very comforted when I think of where I have brought thisngs in just the past
week, WTH YOUR FOLKS HELP THAT IS!!!

Two points on the StartMDE. It would be nice if there was a button that
would "touch" a FE with just a time change to force a replication down. Im
thinking of the YAHOO who opens the his local FE copy and then tries to edit
something. He won't get a corrected copy until I make a change or he/she
calls me and confesses.
I can "force this by simply renaming the master FE and then name it back.
Ithis forces a time change without actually going in and modifying database.
So, somsort of force update force all update would be nice.

I also found out that the Update doesn't work if the FE file is Hidden. The
directory can be hidden, but not the MDB. No biggie. Just got me thinking I
broke something!

Anyway, I'm ready to put this one to rest. Thanks alot!!!!
Great program.

 

[John W. Vinson]

Currently, however, all the FEs are MDBs. I started MDE conversion, but I'm
getting smoked with compliation errors. (agan, not my work here . . .someone
elses). Where I can, I'm fixing. But in some forms I can compile fine, but
the converter still says compilation errors exist.

Check Tony's Corruption FAQ (www.granite.ab.ca/access/corruptmdbs.htm). It has
instructions for Decompiling. You should probably *MAKE A BACKUP* (decompiling
can be dangerous); Compact the database; Decompile it; compact it again; open
the VBA editor and Compile (and fix any compilation errors); then compact yet
once more.

John W. Vinson [MVP]

 

[Tony Toews [MVP]]

Got it! I created copies of all the FEs and put them in folders parallel to
the current productions FEs. I then put copies of the current production FEs
in these folders. Users go right on using the "old" FEs while I run tests on
the new setup. It's running perfect. As I make changes, I see the database
re-copied to the local machine. I lock the FEs, unlock them, initiate the
routine from other desktops. It's all working great.

Glad to hear things are working well.

Two points on the StartMDE. It would be nice if there was a button that
would "touch" a FE with just a time change to force a replication down. Im
thinking of the YAHOO who opens the his local FE copy and then tries to edit
something. He won't get a corrected copy until I make a change or he/she
calls me and confesses.
I can "force this by simply renaming the master FE and then name it back.
Ithis forces a time change without actually going in and modifying database.
So, somsort of force update force all update would be nice.

Yes, that feature is on my wishlist.

I also found out that the Update doesn't work if the FE file is Hidden. The
directory can be hidden, but not the MDB. No biggie. Just got me thinking I
broke something!

Anyway, I'm ready to put this one to rest. Thanks alot!!!!
Great program.

Thanks. Glad to hear it's working for you.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[G-Man]

Tony,

I have the Updater being used in a test group of 8 users.

You know, it works so well, I'm at a loss for the best routine for my
updating the FEs. It seems almost too easy now.

I always have backups, but I assume that if I follow the following
procedure, all will be well.

1. Lock out the db I will be working on via the ini file. This will keep
newcomers from coming in. But current users will be able to go on, since they
are already on with their local copy. No More "I need everybody out of
"such-and such"

2. I make a copy of the object I am going to modify to an "holding database"

3. Modify/add/delete form, query, etc in the "Master" on the network . . . .

4. Exit and turn off the file lock.

That's it? Current users who were on the database during the time I was
modifying it . . . .they will see the changes next time they exit and start
back up.

Done!

 

[Tony Toews [MVP]]

You know, it works so well, I'm at a loss for the best routine for my
updating the FEs. It seems almost too easy now.

1. Lock out the db I will be working on via the ini file. This will keep
newcomers from coming in. But current users will be able to go on, since they
are already on with their local copy. No More "I need everybody out of
"such-and such"

2. I make a copy of the object I am going to modify to an "holding database"

3. Modify/add/delete form, query, etc in the "Master" on the network . . . .

4. Exit and turn off the file lock.

That's it? Current users who were on the database during the time I was
modifying it . . . .they will see the changes next time they exit and start
back up.

That's it.

Alternatively I just work on the FE MDB on my system. I make the MDE
when I'm ready and I copy it to the FE folder file server. I don't
bother setting the lock and unlock flag as copying the file to the
server only takes a few seconds anyhow.

Once a client had a problem. I told them to delete the corrupted MDE
on their system. Then the Auto FE Updater copied down the new MDE
just fine.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm