(UTC)
  Lantica User Forum › Archived Topics › Archived Topics › xlookupsourcelistall question
(Moderator: Forum Admin)
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 Send Topic Send Topic Print Print
Normal Topic xlookupsourcelistall question (Read 2206 times)
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
xlookupsourcelistall question
Sep 23rd, 2004 at 7:02pm
Print Post Print Post  
When using xlookupsourcelistall, I'm seeing something that doesnt seem right:

I'm retrieving 4 fields and getting results each time, but if the fields I'm looking in are blank, my results come back missing data all together. It seems that a 'blank value' should be returned, rather than 'null'(?). This would provide consistency in my results and allow me to better work with the data. Here's an example:

I'm requesting Item name, Cost,Sale price, Retail, MSRP

Here's what I'm getting if LineItem_name2 is NOT on Sale:
LineItem_name;100;149.99;200;300
LineItem_name2;200;300;400
LineItem_name3;300;349.99;400;500

I think that if XlookupSourceListAll finds a blank value, it should return a blank to act as a place holder, so the resulsts should look like this, to keep the data consistent. Note the extra ';'

LineItem_name;100;149.99;200;300
LineItem_name2;200;;300;400
LineItem_name3;300;349.99;400;500

Things get really messy if items dont have MSRPS, or cost is unknown, etc.

Make sense?

Steve
  
Back to top
WWW WWW  
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: xlookupsourcelistall question
Reply #1 - Sep 23rd, 2004 at 7:06pm
Print Post Print Post  
I assume that I can Mass Update all blank fields to be "0" so  it can be a place holder to keep data consistent, but it seems like this is an error in the program.

Any thoughts?

Steve
  
Back to top
WWW WWW  
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: xlookupsourcelistall question
Reply #2 - Sep 23rd, 2004 at 7:31pm
Print Post Print Post  
'Tis fixed in 1.0.5. Comes from not being able to format a blank as a number.
  
Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
WWW WWW  
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: xlookupsourcelistall question
Reply #3 - Sep 23rd, 2004 at 7:33pm
Print Post Print Post  
Sweet. Thanks very much!

Steve
  
Back to top
WWW WWW  
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: xlookupsourcelistall question
Reply #4 - Oct 12th, 2004 at 3:56pm
Print Post Print Post  
I'm seeing a new issue with the following command:

vmasterlist= @xlookupsourcelistall(@fn, mfgr, "sku!vendor", "quality;pattern;color;wide;length;shape;sku")

the xlookup is returning items in the wrong order. wide, length and shape are being returned in the following order:

Length, Shape, Wide.

Will these incorrect results be consistent enough that I can create my own workaround? Will this be fixed for 1.0.5?

Steve
  
Back to top
WWW WWW  
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: xlookupsourcelistall question
Reply #5 - Oct 12th, 2004 at 4:31pm
Print Post Print Post  
I'm not sure if it is just a cut-n-paste error, but the example you cite:

Quote:
vmasterlist= @xlookupsourcelistall(@fn, mfgr, "sku!vendor", "quality;pattern;color;wide;length;shape;sku")


has "wide" in place of "width". Is it really called "wide"?
  
Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
WWW WWW  
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: xlookupsourcelistall question
Reply #6 - Oct 12th, 2004 at 4:40pm
Print Post Print Post  
The db called SKU that the xlookup is looking in was translated from Q&A. The name in Q&A was "width", but Sesame made me change the name.

The FIELD name is still Width, and the Label is still WIDTH, but the LE NAME is now "WIDE". Out of habit, I referred to the term 'width' in my post above.

The xlookup is retrieving all the requested data, its just returning the values in the wrong order. So far, it has been consistent. They are not being randomly jumbled.

Thanks,
Steve
  
Back to top
WWW WWW  
IP Logged
 
The Cow
YaBB Administrator
*****
Offline



Posts: 2530
Joined: Nov 22nd, 2002
Re: xlookupsourcelistall question
Reply #7 - Oct 12th, 2004 at 4:56pm
Print Post Print Post  
I just tried in Customers using 1.0.5 and they are coming back in the order I specified in the call. I even tried renaming an LE, and it still seems to be okay. I also tried it in 1.0.4, and again no problem with order.

Is there anything else about this application that you can think of? If you open the Field Manager (AppName!Manage A Database!Form Name!Manage Fields) in SDesigner, what order does it give the fields bound to those LEs?
  
Mark Lasersohn&&Programmer&&Lantica Software, LLC
Back to top
WWW WWW  
IP Logged
 
Steve_in_Texas
Senior Member
*****
Offline


No personal text

Posts: 893
Location: San Antonio
Joined: Feb 21st, 2004
Re: xlookupsourcelistall question
Reply #8 - Oct 12th, 2004 at 5:30pm
Print Post Print Post  
Mark,

Field manager looked OK, so I dug deeper and realized that I got the fields mixed up when I imported the data from Q&A. (Somehow I lost the records after translation and had to import).

Sorry, again, for the wild goose chase.

Steve
Embarrassed
  
Back to top
WWW WWW  
IP Logged
 
Page Index Toggle Pages: 1
Send Topic Send Topic Print Print
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

Lantica User Forum » Powered by YaBB 2.6.11!
YaBB Forum Software © 2000-2024. All Rights Reserved.

Valid RSS Valid XHTML Valid CSS Powered by Perl Source Forge