J
julia77a
Helo everyone,
I have a difficult problem for which I can't really find any help
anywhere and I'm really confused as to how to approach it.
I have an Access front end application with back end on SQL server.
Some of the tables are local, but most of them are linked tables using
ODBC connection (File DSN). The application was composed of several
smaller databases by my predecessor. I'm not clear as how it happened,
but I assume that at the time of it's upsizing to SQL server data was
append to the new tables from multiple similar tables and therefore the
primary key which is an autonumber contains values ranging anywhere
from -2,146,550,254 to 2,147,433,042, and the table has not even a
100,000 records in it. This one table (called CCTBL) is the worst, but
other tables are just as bad. So, what am I to do to prevent a
disaster, because I'm afraid that one of these days the autonumber will
run out (as it's currently at 2,147,433,042) and the database will go
kabooom. I believe that I need to update the primary keys (autonumber)
using programming language (VBA) starting it at zero (0). But, this
gets more complicated as the primary key in CCTBL is a foreign key in
ContactTBL, which will too need to be updated so that I have a way of
linking these two tables. I have a several other master tables and
their children that will need to be updated in the same way. How and
where do I start? It would be best if I had some script to do it, but
my programming is very basic and I would need some help with that.
Please advise as I'm already loosing my sleep over this. Any help is
appreciated.
Thank you in advance,
Aneta
I have a difficult problem for which I can't really find any help
anywhere and I'm really confused as to how to approach it.
I have an Access front end application with back end on SQL server.
Some of the tables are local, but most of them are linked tables using
ODBC connection (File DSN). The application was composed of several
smaller databases by my predecessor. I'm not clear as how it happened,
but I assume that at the time of it's upsizing to SQL server data was
append to the new tables from multiple similar tables and therefore the
primary key which is an autonumber contains values ranging anywhere
from -2,146,550,254 to 2,147,433,042, and the table has not even a
100,000 records in it. This one table (called CCTBL) is the worst, but
other tables are just as bad. So, what am I to do to prevent a
disaster, because I'm afraid that one of these days the autonumber will
run out (as it's currently at 2,147,433,042) and the database will go
kabooom. I believe that I need to update the primary keys (autonumber)
using programming language (VBA) starting it at zero (0). But, this
gets more complicated as the primary key in CCTBL is a foreign key in
ContactTBL, which will too need to be updated so that I have a way of
linking these two tables. I have a several other master tables and
their children that will need to be updated in the same way. How and
where do I start? It would be best if I had some script to do it, but
my programming is very basic and I would need some help with that.
Please advise as I'm already loosing my sleep over this. Any help is
appreciated.
Thank you in advance,
Aneta