Data Access via ASP

[Punjabi Munda]

Hello alls , i am working on a interanet application for Inventory
handling,
i have a problem while submitting the data to server, please help me?
the problem goes like this
Data base : Ms-Access
Front End : ASP
The problem is how to comit the data "say Invoice" to main database is
two persons tries to make invoice at same time at different computers,
How to maintain the series of Invoice unaffected, how to allocat
Invoice number to them, and how to put a check that both of them can't
make a invoice of same customer at a same time at different computers
Please suggest
thanks
Deepak

[Jon Paal]

--give your invoice table a primary key field which is unique number.
--Make that primary key part of the invoice number.

This way, no two invoices will ever have the same number.
"Punjabi Munda" <de***********@gmail.comwrote in message news:11**********************@b28g2000cwb.googlegr oups.com...

Hello alls , i am working on a interanet application for Inventory
handling,
i have a problem while submitting the data to server, please help me?
the problem goes like this
Data base : Ms-Access
Front End : ASP
The problem is how to comit the data "say Invoice" to main database is
two persons tries to make invoice at same time at different computers,
How to maintain the series of Invoice unaffected, how to allocat
Invoice number to them, and how to put a check that both of them can't
make a invoice of same customer at a same time at different computers
Please suggest
thanks
Deepak

[Deepak Sachdeva]

thanks for your reply but i know this solution , my main question i
think u don't understand, my main problem is if some one tries to make
a invoice from different computer at same time and one who starts
making it first rollback his data before saving it to server, now the
problem exsit that we are already allocate a invoice no. to the same
person, now how to handle this problem
please reply
deepak sachdeva

Jon Paal wrote:

--give your invoice table a primary key field which is unique number.
--Make that primary key part of the invoice number.

This way, no two invoices will ever have the same number.
"Punjabi Munda" <de***********@gmail.comwrote in message news:11**********************@b28g2000cwb.googlegr oups.com...

Hello alls , i am working on a interanet application for Inventory
handling,
i have a problem while submitting the data to server, please help me?
the problem goes like this
Data base : Ms-Access
Front End : ASP
The problem is how to comit the data "say Invoice" to main database is
two persons tries to make invoice at same time at different computers,
How to maintain the series of Invoice unaffected, how to allocat
Invoice number to them, and how to put a check that both of them can't
make a invoice of same customer at a same time at different computers
Please suggest
thanks
Deepak

[Mike Brind]

Jon Paal answered your question correctly. That is how you maintain the
series of invoice numbers and ensure each invoice number is unique.

The question you really should be asking yourself is this: Why would you
allocate an invoice number before an invoice has been successfully created
in a database? Surely, until a user successfully commits their data, no
invoice exists.

--
Mike Brind

"Deepak Sachdeva" <de***********@gmail.comwrote in message
news:11**********************@l12g2000cwl.googlegr oups.com...

thanks for your reply but i know this solution , my main question i
think u don't understand, my main problem is if some one tries to make
a invoice from different computer at same time and one who starts
making it first rollback his data before saving it to server, now the
problem exsit that we are already allocate a invoice no. to the same
person, now how to handle this problem
please reply
deepak sachdeva

Jon Paal wrote:

>--give your invoice table a primary key field which is unique number.
--Make that primary key part of the invoice number.

This way, no two invoices will ever have the same number.
"Punjabi Munda" <de***********@gmail.comwrote in message
news:11**********************@b28g2000cwb.googleg roups.com...

Hello alls , i am working on a interanet application for Inventory
handling,
i have a problem while submitting the data to server, please help me?
the problem goes like this
Data base : Ms-Access
Front End : ASP
The problem is how to comit the data "say Invoice" to main database is
two persons tries to make invoice at same time at different computers,
How to maintain the series of Invoice unaffected, how to allocat
Invoice number to them, and how to put a check that both of them can't
make a invoice of same customer at a same time at different computers
Please suggest
thanks
Deepak

[Deepak Sachdeva]

Hello Mike,
Thanks for your suggestions,
but when user has an interace to make invoice , he must be allocating a
temp invoice number which if he submit the invoice will be invoice
number , but what if he does not, , what if we don't allocate a
invoice number but allocate him a temp. no. which can be a part of
final invoice number, then how do we do it
Deepak Sachdeva

Mike Brind wrote:

Jon Paal answered your question correctly. That is how you maintain the
series of invoice numbers and ensure each invoice number is unique.

The question you really should be asking yourself is this: Why would you
allocate an invoice number before an invoice has been successfully created
in a database? Surely, until a user successfully commits their data, no
invoice exists.

--
Mike Brind

"Deepak Sachdeva" <de***********@gmail.comwrote in message
news:11**********************@l12g2000cwl.googlegr oups.com...

thanks for your reply but i know this solution , my main question i
think u don't understand, my main problem is if some one tries to make
a invoice from different computer at same time and one who starts
making it first rollback his data before saving it to server, now the
problem exsit that we are already allocate a invoice no. to the same
person, now how to handle this problem
please reply
deepak sachdeva

Jon Paal wrote:

--give your invoice table a primary key field which is unique number.
--Make that primary key part of the invoice number.

This way, no two invoices will ever have the same number.
"Punjabi Munda" <de***********@gmail.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...
Hello alls , i am working on a interanet application for Inventory
handling,
i have a problem while submitting the data to server, please help me?
the problem goes like this
Data base : Ms-Access
Front End : ASP
The problem is how to comit the data "say Invoice" to main database is
two persons tries to make invoice at same time at different computers,
How to maintain the series of Invoice unaffected, how to allocat
Invoice number to them, and how to put a check that both of them can't
make a invoice of same customer at a same time at different computers
Please suggest
thanks
Deepak

[Mike Brind]

I have no idea. Why you would want to allocate an invoice number when an
invoice might not be created makes no sense to me at all.

--
Mike Brind
"Deepak Sachdeva" <de***********@gmail.comwrote in message
news:11*********************@h40g2000cwb.googlegro ups.com...

Hello Mike,
Thanks for your suggestions,
but when user has an interace to make invoice , he must be allocating a
temp invoice number which if he submit the invoice will be invoice
number , but what if he does not, , what if we don't allocate a
invoice number but allocate him a temp. no. which can be a part of
final invoice number, then how do we do it
Deepak Sachdeva

Mike Brind wrote:

>Jon Paal answered your question correctly. That is how you maintain the
series of invoice numbers and ensure each invoice number is unique.

The question you really should be asking yourself is this: Why would you
allocate an invoice number before an invoice has been successfully
created
in a database? Surely, until a user successfully commits their data, no
invoice exists.

--
Mike Brind

"Deepak Sachdeva" <de***********@gmail.comwrote in message
news:11**********************@l12g2000cwl.googleg roups.com...

thanks for your reply but i know this solution , my main question i
think u don't understand, my main problem is if some one tries to make
a invoice from different computer at same time and one who starts
making it first rollback his data before saving it to server, now the
problem exsit that we are already allocate a invoice no. to the same
person, now how to handle this problem
please reply
deepak sachdeva

Jon Paal wrote:
--give your invoice table a primary key field which is unique number.
--Make that primary key part of the invoice number.

This way, no two invoices will ever have the same number.
"Punjabi Munda" <de***********@gmail.comwrote in message
news:11**********************@b28g2000cwb.googleg roups.com...
Hello alls , i am working on a interanet application for Inventory
handling,
i have a problem while submitting the data to server, please help
me?
the problem goes like this
Data base : Ms-Access
Front End : ASP
The problem is how to comit the data "say Invoice" to main database
is
two persons tries to make invoice at same time at different
computers,
How to maintain the series of Invoice unaffected, how to allocat
Invoice number to them, and how to put a check that both of them
can't
make a invoice of same customer at a same time at different
computers
Please suggest
thanks
Deepak