This is an excerpt from the ordering system which limits a name to a
single entry. Typically you use something like this in a POS.
In the case of the ordering system we do this so you only get to see
your own name.
sub order_links {
# retrieve order
OE->retrieve_order(\%myconfig, \%$form);
# build the popup menus
$form->{$form->{vc}} = "$form->{name}--$form->{customer_id}";
$form->{"select$form->{vc}"} = "<option
selected>$form->{name}--$form->{customer_id}\n";
$form->{selectcurrency} = "<option selected>USD\n";
}
I just wanted to point out that you can quite easily modify the core with
just a few lines of code in a custom_ script. The overall concept remains
the same, the customer is still in a pull-down menu but there is only one
item now. This let's you work with very large customer tables.
Dieter Simader http://www.sql-ledger.org (780) 472-8161
DWS Systems Inc. Accounting Software Fax: 478-5281
=========== On a clear disk you can seek forever ===========
On Sat, 27 Jul 2002, Ho-Sheng Hsiao wrote:
> On Fri, Jul 26, 2002 at 10:54:06PM +1200, Matt wrote:
> > It has raised one particular point, which is probably generic to any
> > interfacing project, including the SL 'future todo' to create a better
> > customer-selection option than a single (possibly huge) drop-down field.
>
> Yep, I have done exactly that for a customer. This was on the 1.6.x
> series, though. It took me about 20 hours to do it, and a lot of that
> had to do with me not knowing SL while knowing Perl. I made it so that
> the sales associate had to start off by searching for the customer (or
> adding a new customer). It then goes directly to the customer invoice
> screen, with no drop down box.
>
> I had to do this because there were 20,000 some odd customers, with
> more walking in the door every day. (Can you imagine Netscape 4
> rendering that many customers??)
>
> I don't know if this was in the stock 1.8.x series, but if you guys
> are going to scale your stuff to that number, you might want to check
> out the indexing on the SQL side. The stock 1.6.x was extremely slow
> with that large of a dataset, and adding the indexing made the
> response a lot quicker. If the dataset is pretty small, you probably
> won't notice a thing.
>
> -Qaexl-
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> -------------------------------------------------------
> (un)subscribe: http://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> Archive: http://www.mail-archive.com/[email protected]/
>
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
-------------------------------------------------------
(un)subscribe: http://lists.sourceforge.net/lists/listinfo/sql-ledger-users
Archive: http://www.mail-archive.com/[email protected]/
