We use a very simple method for next number when creating customer
ID by utilizing VB field in the company table. There is no locking
but I am sure you could do it by using a checkbox, and some sort of
do until. We don't have to lock since only one person enters these
in now.
Dim compAdapter As CompanyAdapter = New CompanyAdapter
(CustomerEntryForm)
compAdapter.BOConnect()
Dim company As string = "TBT"
Dim CompAd As Boolean = compAdapter.GetByID(company)
Dim CurCustomerID As Integer = compAdapter.CompanyData.Tables
("Company").Rows(0)("Number02")
Dim assignCustId As Integer = CurCustomerID + 1
compAdapter.CompanyData.Tables("Company").Rows(0)("Number02") =
assignCustId
compAdapter.Update()
compAdapter.Dispose()
Dim Customer As EpiDataView = Ctype(oTrans.EpiDataViews
("Customer"),EpiDataView)
txtCustomerId.Text = assignCustId.ToString()
ID by utilizing VB field in the company table. There is no locking
but I am sure you could do it by using a checkbox, and some sort of
do until. We don't have to lock since only one person enters these
in now.
Dim compAdapter As CompanyAdapter = New CompanyAdapter
(CustomerEntryForm)
compAdapter.BOConnect()
Dim company As string = "TBT"
Dim CompAd As Boolean = compAdapter.GetByID(company)
Dim CurCustomerID As Integer = compAdapter.CompanyData.Tables
("Company").Rows(0)("Number02")
Dim assignCustId As Integer = CurCustomerID + 1
compAdapter.CompanyData.Tables("Company").Rows(0)("Number02") =
assignCustId
compAdapter.Update()
compAdapter.Dispose()
Dim Customer As EpiDataView = Ctype(oTrans.EpiDataViews
("Customer"),EpiDataView)
txtCustomerId.Text = assignCustId.ToString()
--- In vantage@yahoogroups.com, "nmtaylor1969" <n.taylor@...> wrote:
>
> That made me laugh Mark... Good response!! ;o)
>
> I am a BPM newbie, so you are way ahead of me at the moment.
>
> You are saying it could be done, right...?
>
> What about creating serial numbers which are prefixed with the job
> number ? Could this be integrated into the job creation logic...?
>
> Have a good weekend...
>
> Nick
>
> --- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@> wrote:
> >
> > > Ideally we just want to use a sequential number and make this
> unique
> > > across all products that we make. In other words if we make
> 100pcs of
> > > product "A" these would have serial numbers 1-100, if we then
make
> > > 100pcs of product "B" these would have serial numbers 101-200
and
> so on.
> >
> > Would that be great!!! UNIQUE serial numbers!!! What a concept!!!
> >
> > <sorry for the sarcasm burst...>
> >
> > > We would like the serial number to be specific to an
individual
> item.
> > > Currently serial number "1" exists for each product in turn,
and
> the
> > > only way to differentiate it is via a different prefix. We are
> finding
> > > this cumbersome to use.
> >
> > Indeed.
> >
> > > Would this be a BPM application...?
> >
> > It would be several. I started with a BPM to ensure that no two
> serialized
> > parts have the same prefix. BUT, that doesn't stop users from
> entering new
> > serial numbers from RMA return or Shipping transactions. So I
> starting to
> > look at a BPM on the Assign Serial Number object or the
> SerialNumber object
> > itself. It won't automatically give you a unique number but it
> would prevent
> > the embarrassing scenario of asking a customer, "OK, that serial
> number
> > belongs to three different parts. Did you buy an X, Y, or a Z?"
(We
> sell to
> > distributors, so we don't always know what an end-user buys.)
> >
> > I was also wondering if it would be possible to use a NUMBER##
> field in the
> > COMPANY record as the next serial number. You'd have to have
some
> locking
> > logic in there in case two users were creating serial numbers at
> the same
> > time though.
> >
> > I'm all for this capability Nick.
> >
> > Mark W.
> >
>