Add letter to end of field

  • Thread starter Thread starter Stepha
  • Start date Start date
S

Stepha

I have a Job_No field that the user enters a number into, then instead of
entering a new number for going back to this original job, they want to
insert a letter at the end. This field Job_No is kept in a Table called
quotation.

e.g. if the Job_no is 22 they want to make the service call on this job 22a
or is 22a has been taken move onto 22b and so on.

If anyone can help me with this it would be appreciated.

TIA
Stephen
 
Stepha said:
I have a Job_No field that the user enters a number into, then instead of
entering a new number for going back to this original job, they want to
insert a letter at the end. This field Job_No is kept in a Table called
quotation.

e.g. if the Job_no is 22 they want to make the service call on this job 22a
or is 22a has been taken move onto 22b and so on.

If anyone can help me with this it would be appreciated.
Click to expand...

If a job can have multiple service calls then their should be a separate
table for this.
The job number would remain the same and the service calls or whatever would
have letters or numbers involved.
These would normally show up in a subform.
If they insist on letters then you would have to write code to assign a
letter to the service call table.
You can do this by using dLast in a query based on that job number. If the
result is null then the letter is "a" else convert the letter to an ASCII
value, add 1 and convert back.
As long as you don't have more than 26 calls you are OK.
If you do the code starts to get complicated and is a lot of busy work.
22a might have been of some value when it was all paperwork but these are
computers.
 
SO do you think it'd be better to do 22.1, 22.2 up to 22.9. I don't believe
that they would do more than 22.9 (or 9 more visits).
 
You will be incrementing the previous value by 1 whether
you use a letter or number. If you are to use numbers you
would probably be better off with 22-1 (or 22-01) rather
than 22.1, as there is less chance of confusion with a
decimal. You can set it up to increment the number or
letter automatically as outlined in the previous reply, so
the user only needs to indicate (by clicking or whatever)
that it is a revisiting of an open job. In this sense it
is less work for the users than the existing system. If
users want to see letters, Access can handle that. If it
doesn't matter, numbers might be easier to work with. The
main thing is that Access can usually adapt to user wishes
and requirements more easily than users can be retrained.
 
Bruce said:
You will be incrementing the previous value by 1 whether
you use a letter or number. If you are to use numbers you
would probably be better off with 22-1 (or 22-01) rather
than 22.1, as there is less chance of confusion with a
decimal. You can set it up to increment the number or
letter automatically as outlined in the previous reply, so
the user only needs to indicate (by clicking or whatever)
that it is a revisiting of an open job. In this sense it
is less work for the users than the existing system. If
users want to see letters, Access can handle that. If it
doesn't matter, numbers might be easier to work with. The
main thing is that Access can usually adapt to user wishes
and requirements more easily than users can be retrained.
Click to expand...

IF there will never be more than 9 it does not matter.
If there is more than 26 then another layer is added since you will need to
go to aa, ab,...

Numbers don't need this, so if I had to pick it would be numbers.

My choice would be to leave them off. All the call can be shown in a subform
arranged by date.
I'll bet a nickel that nobody comes in and says let me see job 22d. They
probably say, let me see the job I did last Thursday which was the 18th.
 
Back
Top