Basic Link Tables Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello all,

I've created an mde version of my Access 2003 database to upload to a
sharepoint site for others to update their information. I then want to be
able to import that information into my mdb database (exact same tables,
etc.) so that I have the latest data available if I need to make any
functionality updates to the mbd table, afterwhich I would re-publish as an
mde file.

I just tested the "Get External Date > Link Tables" function - but instead
of just importing the new data from the mde file, it created new tables
within my mdb database. For instance, one of the tables is called
"tblGroups", and now I also have a "tblGroups1" which was imported from the
mde file. Is there a way to link these directly? Am I doing something wrong?
I'm a relative newbie at this...

Thanks!
 
Update: I also tried the same with the "Get External Data > Import" function,
and that also just creates additional tables (so now I have "tblGroup" and
"tblGroup1" again...) How can I import data into the existing tables directly?

Thanks!
 
Thanks Dave - but I'm not sure how that would work since I'm posting my
database (2003 mde format) to an internal sharepoint site so others can
access it there.

Are you suggesting that I post both the front-end mde and the back-end mdb
to the sharepoint site, and then users would have to download both whenever
they want to make an update? (I assume they wouldn't be able to do much with
just the front-end on sharepoint... especially as the back-end would not be
available on a network drive for the users to link to.)

Ideally I'm trying to keep the back end (relatively) secure, more for the
set-up and functionality than the data itself. The only other option I could
think of would be to split it, post both on the sharepoint but put password
protection on the back-end mdb file - but not sure if that would cause
problems for the users if they don't have the password... any more detailed
suggestions?

Thanks!
 
that is what importing is supposed to do - create the table from the source
database in the destination database. when you *link*, as opposed to
importing, the table is not created, just a link to the table in the source
database is created - but it will have the same name as the source table
(though you can change it).

in either case, importing or linking, you need to run either Append or
Update queries (depending on your needs) to get the imported/linked data in
to your database's native tables.

hth
 
splitting doesn't help anything

moving to SQL Server and usign DTS or SSIS _DOES_ solve the problem
 
Back
Top