Access front & back ends

  • Thread starter Thread starter Tcs
  • Start date Start date
T

Tcs

I have a small app, that is, and will be, just single user. But I want the data
that I create with my code, to be available to others. So I'd like to split my
..mdb into a front and back end.

I have no problem with manually moving the data to the backend mdb. My problem
is, how do I open the backend mdb? Just linked tables? If not, how? I tried
on my own once before, some time ago, and never did have any luck.

Also, how would one "compact & repair" the backend mdb? Now, since my code and
data reside in the *same* mdb, I just have my mdb set to "compact on close".
But if I never interactively open the backend, how does that work?

Thanks in advance, any help is appreciated,

Tom
 
Using linked tables in the front end mdb is exactly what you want to do.
That technique actually makes the changes quite easy, since you're just
moving all of the tables in the back end mdb and creating table links to all
of those tables in the front end. All of your queries and code in the front
end mdb can stay the same.

Even for single user applications, I always recommend using separate back
end and front end mdbs, as you never know in the future when the application
will need to support multiple users.

As far as compacting the back end mdb, I'd recommend scheduling the compacts
to run nightly by using the Scheduled Tasks feature in Windows XP. You'll
need to edit the "advanced properties" of the task to give the necessary
command line arguments. Another option is FMS' tool called Total Visual
Agent. It lets you schedule periodic compacts and repairs and many other
tasks. That option will cost money, though.

Hope that helps,
 
Tcs said:
I have a small app, that is, and will be, just single user. But I want the data
that I create with my code, to be available to others. So I'd like to split my
.mdb into a front and back end.
Click to expand...

Good idea to split, but is it necessary here? Others can access the data
anyway, whether it is in the front or the back.
I have no problem with manually moving the data to the backend mdb. My problem
is, how do I open the backend mdb? Just linked tables? If not, how? I tried
on my own once before, some time ago, and never did have any luck.
Click to expand...

At least from A97 there is a Split wizard. See Help.
Also, how would one "compact & repair" the backend mdb? Now, since my code and
data reside in the *same* mdb, I just have my mdb set to "compact on close".
But if I never interactively open the backend, how does that work?
Click to expand...

You don't need to compact the backend. I hope. It doesn't bloat during
work. The frontend DOES, but you can reach that.
 
Good idea to split, but is it necessary here? Others can access the data
anyway, whether it is in the front or the back.
Click to expand...

I don't want anyone to get at my code. The data I don't care about.
At least from A97 there is a Split wizard. See Help.


You don't need to compact the backend. I hope. It doesn't bloat during
work. The frontend DOES, but you can reach that.
Click to expand...

But if one were to flush the tables in the backend, the space wouldn't be reused
until after it's compacted, no? This app processes a doc file of a database.
As these doc files are updated, I can see wanting to flush the table(s).
 
Tcs said:
I don't want anyone to get at my code. The data I don't care about.
Click to expand...

Consider making it an .mde then. (Keep a .mdb copy for yourself) With a
separate front end you cannot avoid people looking at the code!
But if one were to flush the tables in the backend, the space wouldn't be reused
until after it's compacted, no? This app processes a doc file of a database.
As these doc files are updated, I can see wanting to flush the table(s).
Click to expand...

Ah, I see. Don't have a solution for that. [gear, gear] What if you put
an AutoExec macro in the backend (that fires up the compact process for
it, much the same as in the FE), and Shell it open from the FE?
 
Back
Top