Should I Split It

[S Jackson]

I have a database that is only used by myself and one other user. It is
stored out on our lan. Would it be better to split this database or not
worth the trouble for just the two of us?

TIA
S. Jackson

 

[Kevin3NF]

Yes. Takes 5 minutes to save a lot of hassle.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[S Jackson]

But, I guess my real question is when I tweak a form then I have go
interrupt the other user to implement the change, right?

 

[Kevin3NF]

Or email it to him and let him Save to his drive when convenient. You can't
tweak a form someone else is in now anyway...

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[Douglas J. Steele]

Use the free Auto FE Updater Tony Toews has at
http://www.granite.ab.ca/access/autofe.htm

 

[Cheryl Fischer]

Well, you can probably figure out what my answer to your question is!
<smile>

Sure, go ahead and split this one. Since only two users are running the db,
you have a relatively 'low-risk' project for your first effort at splitting
and deploying the front-end to individual user's computers.

Here's a tip: When you link tables in the back-end to the front-end,
navigate to the database on the server by using Network Neighborhood so that
the link will be the full UNC path. You will avoid individual drive-mapping
problems this way.