Convert linked tables to local tables

[Dhara]

I do a lot of development work in Access 2000. Sometimes our network
is really slow, and makes it impossible to develop. For example, I
have been trying to open a report in design view for half an hour now,
and it still isn't open. When we experience these issues (or when I
need to work from home) I would like to copy the DB to my hard drive
and import all of the linked tables. Is there code that can "convert"
linked tables to local tables? Then I can work locally, which is much
faster, and just import my final product into the real DB.

 

[Albert D. Kallal]

Why on earth go though so much work?

Why not just make a copy of the back end database to your local drive?

In fact, ONE OF THE REASONS why we split is so you can work on a copy of the
data. I suppose it possible that you are a perfect software devleoper, and
NEVER make mistakes. On the other hand, I find it nearly impossible to test,
and debug my code on a live data, espeically those complex deleting routies.

If you have a spit database, and are using ms-access, then you going to be
using the linked table manager on a daily baises, or at least every time you
update your sfotware to your users (or, you complity missed much of the
resasons why you split).

So,

 

[Albert D. Kallal]

Sorry, bumped send key...
Why on earth go though so much work?

Why not just make a copy of the back end database to your local drive?

In fact, ONE OF THE REASONS why we split is so you can work on a copy of the
data. I suppose it possible that you are a perfect software developer, and
NEVER make mistakes. On the other hand, I find it nearly impossible to test,
and debug my code on a live data, especially those complex deleting
routines.

If you have a spit database, and are using ms-access, then you going to be
using the linked table manager on a daily biases, or at least every time you
update your software to your users (or, you complete missed much of the
reasons why you split).

So, simply copy the data to your local machine, and link to that.

You then work on the next great version of the application, and don't
bother, or harm your existing users working on live data. When you finally
have this testing correct (and believe, what a breath of fresh air to be
able to add new records, test deleting, test new code and NOT EVEN HAVE TO
WORRY about cleaning up after making all those test changes to data is a
HUGE relief, and HUGE amount of increase in freedom to develop).

It is WAY WAY too dangerous to develop,a nd test things on the live back
end. (have you really been able to do this now???).

When done, you simply re-link back to the live back end, create the mde and
the re-distribute the mde to each desktop.

I explain this "dance" between your producing back end, and "test" back end
here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Any reason why you are now not currently developing with a copy of the back
end data?

 

[aaron.kempf]

dont listen to these retards.

Use Access Data Projects; you don't have to worry about any of the
local vs linked headaches

-Aaron