473,699 Members | 2,186 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Update foreign key before appending records to central database

Looking for suggestions ----

A database was designed for a national automobile inspection program. In
it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspection
InspectionID
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be completed
for each inspection and the forms would be sent to a central location to be
entered into the database. 50 to 250 inspections would be done at a site and
50 to 250 forms would be entered into the database for each inspection.
There are approximately 70,000 records in the database currently. The number
of inspections has quickly grown to where it will soon be impossible to
enter all the forms into one central database. The plan now is to enter the
inspections into a dozen satellite databases consisting of TblOwner and
TblInspection and then after each inspection send the database file to the
central database location and append the records in TblOwner and
TblInspection into the same named tables in the central database. The
sattelite database location would then be sent an empty satellite database
to repeat the process. OwnerID and InspectionID would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite database
arrives, the OwnerID in TblOwner will start at 1 and end at 250.
Correspondingly , the foreign key, OwnerID in TblInspection, will contain
values of 1 to 250. When TblOwner is appended, all the fields but OwnerID
will be appended to TblOwner in the central database. The Owner records will
have OwnerID values of 70001 to 70250. OwnerID in TblInspection needs to be
updated to the corresponding OwnerID values (70001 to 70250) before the
Inspection records can be appended. The values OwnerID need to be updated to
will continue to increase as each sattelite database arrives. I need
suggestions on how to determine what values to update OwnerID in
TblInspection in the sattelite database to considering that OwnerID in the
TblOwner in the sattelite database may not be contiguous due to the nature
that it's an autonumber field.

Thanks,

Steve
Nov 13 '05 #1
7 2422
Does order of the OwnerID really matter, or can you just create a
random ID for each customer? If you can use random numbers for the
IDs, then I see no reason why creating another field in the parent and
child tables is that big of a deal. Then you can populate the parent
values and cascade them to the children using the existing
relationships. Then if you use the RandomID as your PK in the
different databases, you shouldn't have a problem...

or did I miss a key element here?

Nov 13 '05 #2
Create a set of staging tables with cascading updates
from the primary key field. Import the records to the
staging tables, update the primary key values so that
they don't clash with existing values, then import to
the destination table.

Or use a multifield primary key with a site index.

Or use replication.

Or use random autonumber if you have only 2 or 3 sites.

(replication uses guid's instead of random longs for
more replication sites, but you will regret it if you
try to use guid autonumbers yourself: they are poorly
supported in queries and code)

(david)

"PC Datasheet" <no****@nospam. spam> wrote in message
news:B_******** **********@news read2.news.atl. earthlink.net.. .
Looking for suggestions ----

A database was designed for a national automobile inspection program. In
it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspection
InspectionID
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be completed
for each inspection and the forms would be sent to a central location to
be entered into the database. 50 to 250 inspections would be done at a
site and 50 to 250 forms would be entered into the database for each
inspection. There are approximately 70,000 records in the database
currently. The number of inspections has quickly grown to where it will
soon be impossible to enter all the forms into one central database. The
plan now is to enter the inspections into a dozen satellite databases
consisting of TblOwner and TblInspection and then after each inspection
send the database file to the central database location and append the
records in TblOwner and TblInspection into the same named tables in the
central database. The sattelite database location would then be sent an
empty satellite database to repeat the process. OwnerID and InspectionID
would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite
database arrives, the OwnerID in TblOwner will start at 1 and end at 250.
Correspondingly , the foreign key, OwnerID in TblInspection, will contain
values of 1 to 250. When TblOwner is appended, all the fields but OwnerID
will be appended to TblOwner in the central database. The Owner records
will have OwnerID values of 70001 to 70250. OwnerID in TblInspection needs
to be updated to the corresponding OwnerID values (70001 to 70250) before
the Inspection records can be appended. The values OwnerID need to be
updated to will continue to increase as each sattelite database arrives. I
need suggestions on how to determine what values to update OwnerID in
TblInspection in the sattelite database to considering that OwnerID in the
TblOwner in the sattelite database may not be contiguous due to the nature
that it's an autonumber field.

Thanks,

Steve

Nov 13 '05 #3
My favorite strategy is to use a composite key in the central database that
includes a batch ID and the ID value generated in the remote database. You
generally want the batch ID anyway, so it's not an extra field, though it is a
larger PK index.

On Mon, 12 Sep 2005 14:09:37 GMT, "PC Datasheet" <no****@nospam. spam> wrote:
Looking for suggestions ----

A database was designed for a national automobile inspection program. In
it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspectio n
InspectionID
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be completed
for each inspection and the forms would be sent to a central location to be
entered into the database. 50 to 250 inspections would be done at a site and
50 to 250 forms would be entered into the database for each inspection.
There are approximately 70,000 records in the database currently. The number
of inspections has quickly grown to where it will soon be impossible to
enter all the forms into one central database. The plan now is to enter the
inspections into a dozen satellite databases consisting of TblOwner and
TblInspectio n and then after each inspection send the database file to the
central database location and append the records in TblOwner and
TblInspectio n into the same named tables in the central database. The
sattelite database location would then be sent an empty satellite database
to repeat the process. OwnerID and InspectionID would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite database
arrives, the OwnerID in TblOwner will start at 1 and end at 250.
Correspondingl y, the foreign key, OwnerID in TblInspection, will contain
values of 1 to 250. When TblOwner is appended, all the fields but OwnerID
will be appended to TblOwner in the central database. The Owner records will
have OwnerID values of 70001 to 70250. OwnerID in TblInspection needs to be
updated to the corresponding OwnerID values (70001 to 70250) before the
Inspection records can be appended. The values OwnerID need to be updated to
will continue to increase as each sattelite database arrives. I need
suggestions on how to determine what values to update OwnerID in
TblInspectio n in the sattelite database to considering that OwnerID in the
TblOwner in the sattelite database may not be contiguous due to the nature
that it's an autonumber field.

Thanks,

Steve


Nov 13 '05 #4
David,

Thanks for responding. Could you give more details about your staging tables
concept.

Thanks!

Steve
"david epsom dot com dot au" <david@epsomdot comdotau> wrote in message
news:43******** *************** @lon-reader.news.tel stra.net...
Create a set of staging tables with cascading updates
from the primary key field. Import the records to the
staging tables, update the primary key values so that
they don't clash with existing values, then import to
the destination table.

Or use a multifield primary key with a site index.

Or use replication.

Or use random autonumber if you have only 2 or 3 sites.

(replication uses guid's instead of random longs for
more replication sites, but you will regret it if you
try to use guid autonumbers yourself: they are poorly
supported in queries and code)

(david)

"PC Datasheet" <no****@nospam. spam> wrote in message
news:B_******** **********@news read2.news.atl. earthlink.net.. .
Looking for suggestions ----

A database was designed for a national automobile inspection program. In
it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspection
InspectionID
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be
completed for each inspection and the forms would be sent to a central
location to be entered into the database. 50 to 250 inspections would be
done at a site and 50 to 250 forms would be entered into the database for
each inspection. There are approximately 70,000 records in the database
currently. The number of inspections has quickly grown to where it will
soon be impossible to enter all the forms into one central database. The
plan now is to enter the inspections into a dozen satellite databases
consisting of TblOwner and TblInspection and then after each inspection
send the database file to the central database location and append the
records in TblOwner and TblInspection into the same named tables in the
central database. The sattelite database location would then be sent an
empty satellite database to repeat the process. OwnerID and InspectionID
would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite
database arrives, the OwnerID in TblOwner will start at 1 and end at 250.
Correspondingly , the foreign key, OwnerID in TblInspection, will contain
values of 1 to 250. When TblOwner is appended, all the fields but OwnerID
will be appended to TblOwner in the central database. The Owner records
will have OwnerID values of 70001 to 70250. OwnerID in TblInspection
needs to be updated to the corresponding OwnerID values (70001 to 70250)
before the Inspection records can be appended. The values OwnerID need to
be updated to will continue to increase as each sattelite database
arrives. I need suggestions on how to determine what values to update
OwnerID in TblInspection in the sattelite database to considering that
OwnerID in the TblOwner in the sattelite database may not be contiguous
due to the nature that it's an autonumber field.

Thanks,

Steve


Nov 13 '05 #5
Steve,

Thank you for responding! Your startegy seems like it would be good if
starting from scratch but im this case the first batch of owner records will
be appended to the central database and their OwnerIDs will become 70001 to
70250. The foreign key in the inspection records must then take on these
same values.

Steve
"Steve Jorgensen" <no****@nospam. nospam> wrote in message
news:gi******** *************** *********@4ax.c om...
My favorite strategy is to use a composite key in the central database
that
includes a batch ID and the ID value generated in the remote database.
You
generally want the batch ID anyway, so it's not an extra field, though it
is a
larger PK index.

On Mon, 12 Sep 2005 14:09:37 GMT, "PC Datasheet" <no****@nospam. spam>
wrote:
Looking for suggestions ----

A database was designed for a national automobile inspection program. In
it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspecti on
InspectionI D
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be completed
for each inspection and the forms would be sent to a central location to
be
entered into the database. 50 to 250 inspections would be done at a site
and
50 to 250 forms would be entered into the database for each inspection.
There are approximately 70,000 records in the database currently. The
number
of inspections has quickly grown to where it will soon be impossible to
enter all the forms into one central database. The plan now is to enter
the
inspections into a dozen satellite databases consisting of TblOwner and
TblInspecti on and then after each inspection send the database file to the
central database location and append the records in TblOwner and
TblInspecti on into the same named tables in the central database. The
sattelite database location would then be sent an empty satellite database
to repeat the process. OwnerID and InspectionID would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite
database
arrives, the OwnerID in TblOwner will start at 1 and end at 250.
Corresponding ly, the foreign key, OwnerID in TblInspection, will contain
values of 1 to 250. When TblOwner is appended, all the fields but OwnerID
will be appended to TblOwner in the central database. The Owner records
will
have OwnerID values of 70001 to 70250. OwnerID in TblInspection needs to
be
updated to the corresponding OwnerID values (70001 to 70250) before the
Inspection records can be appended. The values OwnerID need to be updated
to
will continue to increase as each sattelite database arrives. I need
suggestions on how to determine what values to update OwnerID in
TblInspecti on in the sattelite database to considering that OwnerID in the
TblOwner in the sattelite database may not be contiguous due to the nature
that it's an autonumber field.

Thanks,

Steve

Nov 13 '05 #6
Make a copy of the source tables. You can use the
source database, destination database, or third database.

Make sure the tables have cascading update defined
on the relationships. (Change if necessary)
Create an update query for the primary table, which
updates the primary key to [original value] + [offset]
Get the offset in the query by using DMAX() on the
destination table. The cascading update will fix
the dependant tables.

After you have updated the staging tables,
append to the destination tables

Then delete the values from the staging tables,
or discard the database.

(david)

"PC Datasheet" <no****@nospam. spam> wrote in message
news:7B******** **********@news read2.news.atl. earthlink.net.. .
David,

Thanks for responding. Could you give more details about your staging
tables concept.

Thanks!

Steve
"david epsom dot com dot au" <david@epsomdot comdotau> wrote in message
news:43******** *************** @lon-reader.news.tel stra.net...
Create a set of staging tables with cascading updates
from the primary key field. Import the records to the
staging tables, update the primary key values so that
they don't clash with existing values, then import to
the destination table.

Or use a multifield primary key with a site index.

Or use replication.

Or use random autonumber if you have only 2 or 3 sites.

(replication uses guid's instead of random longs for
more replication sites, but you will regret it if you
try to use guid autonumbers yourself: they are poorly
supported in queries and code)

(david)

"PC Datasheet" <no****@nospam. spam> wrote in message
news:B_******** **********@news read2.news.atl. earthlink.net.. .
Looking for suggestions ----

A database was designed for a national automobile inspection program. In
it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspection
InspectionID
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be
completed for each inspection and the forms would be sent to a central
location to be entered into the database. 50 to 250 inspections would be
done at a site and 50 to 250 forms would be entered into the database
for each inspection. There are approximately 70,000 records in the
database currently. The number of inspections has quickly grown to where
it will soon be impossible to enter all the forms into one central
database. The plan now is to enter the inspections into a dozen
satellite databases consisting of TblOwner and TblInspection and then
after each inspection send the database file to the central database
location and append the records in TblOwner and TblInspection into the
same named tables in the central database. The sattelite database
location would then be sent an empty satellite database to repeat the
process. OwnerID and InspectionID would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite
database arrives, the OwnerID in TblOwner will start at 1 and end at
250. Correspondingly , the foreign key, OwnerID in TblInspection, will
contain values of 1 to 250. When TblOwner is appended, all the fields
but OwnerID will be appended to TblOwner in the central database. The
Owner records will have OwnerID values of 70001 to 70250. OwnerID in
TblInspection needs to be updated to the corresponding OwnerID values
(70001 to 70250) before the Inspection records can be appended. The
values OwnerID need to be updated to will continue to increase as each
sattelite database arrives. I need suggestions on how to determine what
values to update OwnerID in TblInspection in the sattelite database to
considering that OwnerID in the TblOwner in the sattelite database may
not be contiguous due to the nature that it's an autonumber field.

Thanks,

Steve



Nov 13 '05 #7
Thanks, David, appreciate the help!

Steve

"david epsom dot com dot au" <david@epsomdot comdotau> wrote in message
news:43******** *************** @lon-reader.news.tel stra.net...
Make a copy of the source tables. You can use the
source database, destination database, or third database.

Make sure the tables have cascading update defined
on the relationships. (Change if necessary)
Create an update query for the primary table, which
updates the primary key to [original value] + [offset]
Get the offset in the query by using DMAX() on the
destination table. The cascading update will fix
the dependant tables.

After you have updated the staging tables,
append to the destination tables

Then delete the values from the staging tables,
or discard the database.

(david)

"PC Datasheet" <no****@nospam. spam> wrote in message
news:7B******** **********@news read2.news.atl. earthlink.net.. .
David,

Thanks for responding. Could you give more details about your staging
tables concept.

Thanks!

Steve
"david epsom dot com dot au" <david@epsomdot comdotau> wrote in message
news:43******** *************** @lon-reader.news.tel stra.net...
Create a set of staging tables with cascading updates
from the primary key field. Import the records to the
staging tables, update the primary key values so that
they don't clash with existing values, then import to
the destination table.

Or use a multifield primary key with a site index.

Or use replication.

Or use random autonumber if you have only 2 or 3 sites.

(replication uses guid's instead of random longs for
more replication sites, but you will regret it if you
try to use guid autonumbers yourself: they are poorly
supported in queries and code)

(david)

"PC Datasheet" <no****@nospam. spam> wrote in message
news:B_******** **********@news read2.news.atl. earthlink.net.. .
Looking for suggestions ----

A database was designed for a national automobile inspection program.
In it's simplest form, the database has two tables:
TblOwner
OwnerID
<Year/Make/Model owned by owner, Owner name/address, etc)

TblInspection
InspectionID
OwnerID
<~50 inspection results>

Originally, inspections would be done at a site, a form would be
completed for each inspection and the forms would be sent to a central
location to be entered into the database. 50 to 250 inspections would
be done at a site and 50 to 250 forms would be entered into the
database for each inspection. There are approximately 70,000 records in
the database currently. The number of inspections has quickly grown to
where it will soon be impossible to enter all the forms into one
central database. The plan now is to enter the inspections into a dozen
satellite databases consisting of TblOwner and TblInspection and then
after each inspection send the database file to the central database
location and append the records in TblOwner and TblInspection into the
same named tables in the central database. The sattelite database
location would then be sent an empty satellite database to repeat the
process. OwnerID and InspectionID would start over at 1.

The problem is in the appending process. With 70,000 records, the last
OwnerID is 70,000 at this point in time. When the first sattellite
database arrives, the OwnerID in TblOwner will start at 1 and end at
250. Correspondingly , the foreign key, OwnerID in TblInspection, will
contain values of 1 to 250. When TblOwner is appended, all the fields
but OwnerID will be appended to TblOwner in the central database. The
Owner records will have OwnerID values of 70001 to 70250. OwnerID in
TblInspection needs to be updated to the corresponding OwnerID values
(70001 to 70250) before the Inspection records can be appended. The
values OwnerID need to be updated to will continue to increase as each
sattelite database arrives. I need suggestions on how to determine what
values to update OwnerID in TblInspection in the sattelite database to
considering that OwnerID in the TblOwner in the sattelite database may
not be contiguous due to the nature that it's an autonumber field.

Thanks,

Steve



Nov 13 '05 #8

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
36254
by: Ralph Smith | last post by:
I'm having trouble copying a database to another machine. Here are the two table's in ths database and the sql commands: DROP TABLE IF EXISTS `clients`; CREATE TABLE `clients` ( `client_id` int(10) unsigned NOT NULL auto_increment, `lastname` char(15) NOT NULL default '', `firstname` char(15) NOT NULL default '', `birthdate` date NOT NULL default '0000-00-00',
16
17011
by: Philip Boonzaaier | last post by:
I want to be able to generate SQL statements that will go through a list of data, effectively row by row, enquire on the database if this exists in the selected table- If it exists, then the colums must be UPDATED, if not, they must be INSERTED. Logically then, I would like to SELECT * FROM <TABLE> WHERE ....<Values entered here>, and then IF FOUND UPDATE <TABLE> SET .... <Values entered here> ELSE INSERT INTO <TABLE> VALUES <Values...
9
4351
by: Dom Boyce | last post by:
Hi First up, I am using MS Access 2002. I have a database which records analyst rating changes for a list of companies on a daily basis. Unfortunately, the database has been set up (by my predecessor, I hasten to add) so that each day it creates a copy of the record for each company, changes the date to today's date, and prompts the user for any changes of ratings on that day. The resulting data table grows by approx 600 records per...
33
4284
by: Lee C. | last post by:
I'm finding this to be extremely difficult to set up. I understand that Access won't manage the primary key and the cascade updates for a table. Fine. I tried changing the PK type to number and setting default value to a UDF that manages the auto-numbering. Access won't take a UDF as a default value. Okay, I'll use SQL WITHOUT any aggregate functions, for the default value. Access won't do that either. Okay, I create a second...
0
5815
by: M. David Johnson | last post by:
I cannot get my OleDbDataAdapter to update my database table from my local dataset table. The Knowledge Base doesn't seem to help - see item 10 below. I have a Microsoft Access 2000 database which indexes computer magazine articles for personal reference. I am developing a Visual Basic.NET program whose sole purpose is to enter new records into the database. No updates to existing entries, no deletions, and no display
30
3393
by: Charles Law | last post by:
Here's one that should probably have the sub-heading "I'm sure I asked this once before, but ...". Two users are both looking at the same data, from a database. One user changes the data and commits it. How does the other user get the updated view without polling for changes? Is there some sort of callback mechanism that can be set up on the dataset or connection? TIA
0
1700
by: jon | last post by:
Hi there, I'm brand new to Access and may be trying to do too much too soon, but I wanted to get some expert advice on how the best way to go about what I am trying to accomplish would be. I am trying to modify the Microsoft Template at the following address (http://office.microsoft.com/en-us/templates/TC012186931033.aspx?CategoryID=CT101426031033) to work as an issues tracker that imports and updates the issues from a SQL 2005...
1
7031
by: jeffro | last post by:
I have a database used for recording survey data. In the database, I have a form that displays a survey participant and a subform that is filled in by selecting a question from a looklist and then a response. The questions are held in a table and they are always the same. This is what I want to do. I want a button on the main form that can be clicked, When click, It will populate the survey detail table with the id of the record...
16
3501
by: ARC | last post by:
Hello all, So I'm knee deep in this import utility program, and am coming up with all sorts of "gotcha's!". 1st off. On a "Find Duplicates Query", does anyone have a good solution for renaming the duplicate records? My thinking was to take the results of the duplicate query, and somehow have it number each line where there is a duplicate (tried a groups query, but "count" won't work), then do an update query to change the duplicate to...
0
8622
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
0
9184
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. Here is my compilation command: g++-12 -std=c++20 -Wnarrowing bit_field.cpp Here is the code in...
0
9045
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth. The Art of Business Website Design Your website is...
1
8930
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
0
8892
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
1
6538
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms. Adolph will...
0
4381
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
1
3061
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
2
2358
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.