Sharing app across network - incomplete database

[willkr]

I have an app that resides on my computer in a home network and I want my wife to be able to access it from her computer (also on the network). I set-up a network share and gave her access. Now she can run the app from her computer. However ----- the database appears incomplete. It only shows data up until about a certain date. Everything on the app works, but the database is incomplete.



Any ideas?

Willkr

[willkr]

I have read that in this situation I need to put the front end on each system and leave the back-end on my system. I tried just copying the .accdb to the other system, but I still only get a partial database. How do I put just the front end on the other system?

willkr

[CJ_London]

Split it first the backend just has tables, the front end, everything else

[Micron]

Maybe you've connected her copy to the wrong set of tables (an older backup of your complete db)?

[willkr]

I have split it. Do I just load the .accdb file on her computer? How do I then connect it to the backend

[Micron]

How do I then connect it to the backend

Ribbon>External Data>New Data Source>From Database>Access and choose to link, not import.
or google the question?

Do I just load the .accdb file on her computer?

Aren't both files accdb? The proper terminology is front end, back end or fe,be for short. That way people will know what you're asking. accdb doesn't really matter.

[ArviLaanemets]

As there was said before, you have to split your database (DB) to back-end DB (BE) and front-end DB (FE). BE contains tables which must be accessible for all users. It also can contain saved queries, but with Access BE this probably will be not very good idea. FE contains rest of your app (Forms, Reports, Queries and VBA modules where you store VBA procedures and User Defined Functions (UDF). It also contains links to all tables (and queries) you have in BE. When you open a FE, you see those links as ordinary tables (but you can't edit their structure).

The BE must be placed in location available for all users in your local (home) network. Every user must have his/her own copy of FE in available location in your local (home) network.

When you split Access DB where the FE is stored on some sheared (server) resource, then creating new FE copies will be simply making a copy of existing one - for all users the BE will have the same address. I have no experience designing Access apps for home network, but I suspect when you have both BE and FE on your HD, simply copy-paste will not work. You have to update all links in other user's FE.

A probable workaround will be, that you try to define the folder in your computer, where you will have your BE, as linked resource (like X: ). And then in another computer, you also link this folder in same way (I'm not sure this will work, but you can try). Now after you create your 1st FE, you probably can make a second working one simply using copy-paste (because the BE address will be same for both of you, and your wife).

Another option which may work will be any storage device in your home network with access for all users there. You simply place your BE there.

[Welshgasman]

I have an app that resides on my computer in a home network and I want my wife to be able to access it from her computer (also on the network). I set-up a network share and gave her access. Now she can run the app from her computer. However ----- the database appears incomplete. It only shows data up until about a certain date. Everything on the app works, but the database is incomplete.

Any ideas?

Willkr

Do you make backups?
I'd also say probably the wrong file.

Whilst if you both need to use it at the same time, you need to split it. I would get it working one person at a time first, else you end up linking to the incorrect file (BE) still?

[willkr]

OK, I relinked the BE to the FE on her system and now it works. Thanks to all for your help

[Micron]

So you had linked the wrong tables then?

[willkr]

No, I hadn't linked them at all. I had originally copied the entire directory to her system and it contained both the fe and be with links to the home directory. Once I relinked it to the shared directory on my system it worked fine.

[Micron]

Isn't that saying the same thing? It may have been the same file name, maybe even the same path but certainly a different hard drive?

[willkr]

Hair splitting is not my thing, but since you insist: Your comment, "So you had linked the wrong tables then?" implies that I actively linked the wrong tables. When I originally linked the fe and be they were in the same directory on the same hard drive and were correctly linked. When I moved the app to her computer I did not actively link anything, not realizing that they were now already linked to the wrong be. So, NO, I had not linked the wrong tables, it was linked to the wrong tables by virtue of my moving the app to a new computer.

The bottom line is that I had to link the tables to the shared drive.

END OF DISCUSSION!

[Micron]

Don't worry - won't happen again.