Search options (Page 16 of 25)

Very creative Manix and Brian.

See attached.

frmInvoice.cbSIcustCountry.dbItemID := -1;

This clears the dbitemid. For a new sale it was not cleared and showing a country for an empty customer.

Unfortunately you cannot change the font attributes on individual lines inside a memo field. What I did in the attached project is removed the memo field and created a panel with supplier labels inside it. Visually it looks the same with the exception that you can control fonts, colors, etc on the labels.

I took care of this through script.

I also took care of this. However, I know you are trying to learn various techniques and ways to do things, but you should try to stay away from doing extraneous SqlExecutes to retrieve data when MVD already has retrieved the data through normal processes.

Yes you can. Use the following:

frmInvoice.Memo1.Lines.add(.....);

Replace the dots with your data, either form fields or SqlExecute to retrieve the data. You need this line for each item (Name,Address,City, etc)

Check out the attached for a possible solution for the items of concern. No1, I don't think it's practical to have users put in new purchase invoices after a sale. No 2, the solution takes care of the traceability issue as Derek astutely pointed out. Basically a purchase invoice is maintained in play when a sale takes place. In other words, a sale will create a new sale invoice record while the purchase invoice remains in tact as is.

Adam and Derek,

I may have the solution to both. Since I'm not sure how MVD constructs the sql when you have the same tablegrid also as the search. Its hard to say what its doing behind the scenes. So what I did was put together the query on the button. Doing this I know what its going to display.

I also fixed the tax rate problem. Derek was right. You have to get to the tax rate through the invoice.

My internet service had been going in and out so my fix is on my previous post. I wasn't able to get to Derek's solution.

Adam,

I added a line to your purchase refund and a line to your sale refund. Look for "EHW - Added the following line". Also, I commented out a couple of lines on the refund buttons click event. They were not needed.

It's fixed.  See attached.

David,

Make sure you place the $ sign in both the tablegrid settings and the Search button settings. I tested it and it works fine.

Interesting there Derek. I understand what you want to do and I don't have an answer either. Apparently the "SelectedRow" property does not get updated till the full click (down and up) is completed.  So hopefully Dimitry will have a way to do it. It actually could be the beginning stages of a drag and drop type functionality as well.

For the challenge I put together a kind of alternative to your situation. I'm sure you probably already tested various scenarios including what I have so my alternative will probably not be right for your project, but I included it here in case it may be a fit for someone else's projects.

A click on the magnifying glass in the tablegrid will show the call memo. Another click anywhere except the magnifying glass on another row will remove the memo.

Don't mean to step on your toes Derek. I had a couple of minutes to look at the project.  Adam, I think the problem lies with the ShowRecord on your hidden buttons plus the fields at the bottom of the form being directly linked to the database table. The ShowRecord is populating the fields at the bottom of each of the tabsheets as well as the search fields and that's what is messing up the tablegrid displays as you mentioned with incremental searches. I removed the linking of the fields to the table. I also removed the ShowRecord action from the hidden buttons and replaced it with script to populate the fields at the bottom of the tabsheets with the entries in the respective tablegrid. Hopefully I'm on target with the problem and solution for you.

Derek, if you have another way, by all means include it. I know there is usually more than one way to solve things in MVD.

Adam,
There's not a whole lot you can do with disabled components when it involves events. You could use popup hints but all the components would need to be set to ReadOnly and not disabled. Groupboxes cannot be set to Readonly. Each field would need to be set to Readonly. Since you said that your project would contain a lot of fields, it may not be feasible to do it this way. The closest I could come up with to do what you are looking for is attached. The combobox needs to be the first field to have focus on the form.

DBK, Derek,

I threw together a quick project to demonstrate a possible solution for you. First and foremost this project is by no means anywhere close to a productional app. My solution is along the same lines as to what Derek mentioned. I used a slightly different approach than the normal combobox methodology in MVD. The combobox for products is still there in order to make the connection to invoice items, but it is hidden. The lookup is done using a tablegrid instead. So on the invoice detail form the user can either type in a freeform text field or do a lookup into the product table. The lookup will fill in the invoice line item text field and price field from the product table. The invoice detail form will let you know whether you have a stock item or a non-stock item. If you have a stock item assigned to the line, you have the ability through a button to remove the stock item and put in a freeform text description in it's place. Hope it helps. If not, it was good practice for me anyway. LOL.