About Tom's sorting question

[Chuck]

About Tom's sorting question.

Is it possible that Tom is tackling this problem the wrong way?

How is Tom going to use a report with 24000+ part numbers?
Trying to find a specific part number in a 2500+ page printed report is not
very productive. Trying to find a specific part number in an electronic report
is no better unless you set up a search function. If you have a search
function, you don't need to sort the part numbers at all.

My suggestion would be to make a form where you could enter the part number in
a text box. Add a command button to open a report. Make the data source for
the report a query. Get the criteria for the part number from the text box in
the form.

Example: enter PGD502QS in the text box. In the query, set the criteria for
the for the part number [Forms]![<your form name>]![<your text box name>]
When you click the command button to open the report, the report will look at
the query for is data. The query will look at the text box in the form for its
criteria. The report can be designed to show the data in all fields associated
with the single part number.

Chuck
--

 

[Tom]

Chuck,

It's not about finding a number amongst other numbers. It's about the way
the numbers are arranged on a shelf, in chronological part number or price
sheet sequence. The same for any competitor. We use number sequences in
all reports and label making and makes things very logical to deal with.
Sometimes, I have to deal with a competitor's numbers in sequence and other
times, I have to deal with my part numbers in sequence. The table I
provided offers some insights into the various types of numbers I have to
deal with on both sides.

Some jobs would only deal with 5,000 numbers, another more or less. A
warehouse might have 10,000 to 15,000. Each job will be different based on
the available part numbers on the shelf, but if the sort routine can handle
any type of number, then that would be ideal. If we have to throw out
certain numbers patterns due to complexity, that's fine. Hopefully, we can
accommodate all of my company's number patterns.

Hope this helps!

Thx for your input and assistance!

Tom

About Tom's sorting question.

Is it possible that Tom is tackling this problem the wrong way?

How is Tom going to use a report with 24000+ part numbers?
Trying to find a specific part number in a 2500+ page printed report is not
very productive. Trying to find a specific part number in an electronic report
is no better unless you set up a search function. If you have a search
function, you don't need to sort the part numbers at all.

My suggestion would be to make a form where you could enter the part number in
a text box. Add a command button to open a report. Make the data source for
the report a query. Get the criteria for the part number from the text box in
the form.

Example: enter PGD502QS in the text box. In the query, set the criteria for
the for the part number [Forms]![<your form name>]![<your text box name>]
When you click the command button to open the report, the report will look at
the query for is data. The query will look at the text box in the form for its
criteria. The report can be designed to show the data in all fields associated
with the single part number.

Chuck

 

[Larry Linson]

It's really helpful, if you respond to a question instead of including a
text reference to it. It is somewhat surprising that even Tom saw and
responded to this. In the batch of posts where I saw it, I had over 500
unread posts just in this newsgroup alone.

Larry Linson
Microsoft Access MVP