(UTC)
(Moderator: Forum Admin)
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 [2]  Send Topic Send Topic Print Print
Hot Topic (More than 10 Replies) baby step (Read 13979 times)
lksseven
Full Member
***
Offline



Posts: 416
Location: Southwest
Joined: Jan 26th, 2009
Re:  baby step
Reply #15 - Feb 12th, 2009 at 10:32pm
Print Post Print Post  
Bharat,

I appreciate your help!!!!!

so my application, wc2.db, is comprised of the following databases:
Client
Inventory
Orders (subform SOLines)
Purch (subform POLines)
Pricing
Vendors
Trucks (subform TruckLines).

so if I want to have TruckLines (subform to Trucks) pull from Inventory!ItemDesc, should the Xlookup programming begin (@fn .....  ?
        

btw, I have bound those fields, and still no joy.

Obviously I have miles to go.  I promise I won't be this wordy/needy after I get past 2+2=4  Cry
  
Larry
Back to top
WWW WWW YIM YIM  
IP Logged
 
lksseven
Full Member
***
Offline



Posts: 416
Location: Southwest
Joined: Jan 26th, 2009
Re:  baby step
Reply #16 - Feb 12th, 2009 at 10:47pm
Print Post Print Post  
yikes, hold the phone.   I think my wc2.db was locked.  I unlocked it - let me try the programming again.  I'll report back.

Undecided
  
Larry
Back to top
WWW WWW YIM YIM  
IP Logged
 
lksseven
Full Member
***
Offline



Posts: 416
Location: Southwest
Joined: Jan 26th, 2009
Re:  baby step
Reply #17 - Feb 12th, 2009 at 11:09pm
Print Post Print Post  
it worked.   Unlocking the wc2.db and then binding the fields to the elements, and then re-entering the programming worked.

Sorry for my brickhead - I feel like a raw recruit on the first day of rifle training (hey, Sarg, what's this thing do?   "Bang!" )

Bharat, I still don't understand the drawback of using xlookup to pull in the ItemDesc that accompanies ItemNum.
  
Larry
Back to top
WWW WWW YIM YIM  
IP Logged
 
Bharat_Naik
Senior Member
Members
*****
Offline


Ever ready to learn and
share

Posts: 1202
Location: Chicago,  Illinois
Joined: Dec 16th, 2003
Re:  baby step
Reply #18 - Feb 12th, 2009 at 11:35pm
Print Post Print Post  
I am glad it worked for you.

xlookup ( ) command will place the value in the ItemDesc element...  but here in the subform there are many elements named ItemDesc, one per each lineItem or record in the subform. That is why the Fieldvalue of ItemDesc element in first record is @FormFieldValue ("TruckLines", "Itemdesc", 1).  Now when you want to assign the value you have to use FormFieldValue ( ).  The same as difference between @xlookup ( ) and xlookup ( ).

I am not very good at explaining. I am sure someone will step in and do a lot better job.
  
Back to top
 
IP Logged
 
lksseven
Full Member
***
Offline



Posts: 416
Location: Southwest
Joined: Jan 26th, 2009
Re:  baby step
Reply #19 - Feb 12th, 2009 at 11:55pm
Print Post Print Post  
I will read up on @FormFieldValue this evening.

Have a great evening!
  
Larry
Back to top
WWW WWW YIM YIM  
IP Logged
 
Ben
Lantica Support
*****
Offline



Posts: 218
Joined: Apr 7th, 2005
Re:  baby step
Reply #20 - Feb 13th, 2009 at 6:44pm
Print Post Print Post  
Quote:
xlookups would not work without that.


Bharat,
If the programming is in the subform referencing the subform lksseven will not need to use FormFieldValue. @XLookup or the XResultSetValue command would work.
  
Back to top
WWW WWW  
IP Logged
 
lksseven
Full Member
***
Offline



Posts: 416
Location: Southwest
Joined: Jan 26th, 2009
Re:  baby step
Reply #21 - Feb 13th, 2009 at 7:25pm
Print Post Print Post  
Thanks, Ben!

Bharat,  your advice was put to good use - I was studying up on FormFieldValue last night and have a much better understanding of it now.  Thanks for the pointer.
  
Larry
Back to top
WWW WWW YIM YIM  
IP Logged
 
Page Index Toggle Pages: 1 [2] 
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