Reputation: 574 Enlightened
- Active Posts:
- 3,001 (1.47 per day)
- 19-May 09
- Profile Views:
- Last Active:
- Jul 28 2014 10:19 PM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Who Cares
- Favorite Gaming Platform:
- Your Car:
- Dream Kudos:
- Expert In:
Posts I've Made
Posted 28 Jul 2014To understand how to apply it to VB6, investigate ADO.
Posted 28 Jul 2014Glad you sorted.
I found this link but if it confuses you'll have to continue searching. Aren't you already reading a book or taking a tutorial?
In the link it uses "SELECT * FROM Employees". For a single record it could be:
SELECT FirstName, LastName FROM Employees WHERE EmployeeID = 54
You can also use
SELECT TOP 1 * from Employeesif you don't care which record you get and don't know anything about the data. That will give you the first one.
Posted 28 Jul 2014As it turns out, my question has its basis in a misunderstanding. When I first got my Export method to work at all, it was with this format:
public void Export<Category>(someCategoryList, "C:\Temp2\myFile.txt", 0)
I wanted to know how I could plug different values in for <Category> without explicitly doing so at design time with some sort of ever-expanding switch statement. As it turns out, this works fine:
public void Export(someCategoryList, "C:\Temp2\myFile.txt", 0)
so the problem is moot. I've already been able to derive the right List ("someCategoryList" in my example) using Reflection, so problem solved.
Thanks for your ideas, thlin and curtis. thlin, I couldn't put an IEnumerable, because it's an IEnumerable<> and I would have to stick the object into the <>. The whole goal is to not have to do that, injecting the right objects in polymorphically at runtime. So that was no go. Curtis, I'm working on one level of abstraction over that one. Suppose Main is a worker method for a thread, and what you have to work with is a ThreadParameter object that says which method you're going to call in yet another object to return an object that you will then pass to your DoSomething method, that's the architecture I'm going for. So yeah, then I have to cast the list to a type I only know at runtime.
Interestingly, as is sometimes the case, the solution is to pass nothing at all. />
Posted 21 May 2014First break the interface down into parts. How many parts (forms, reports, whatever) are there? Modi has given you a rough mockup of the part identified in your last sentence. What are the others? Describe them. Once you have those, you're on your way. Take all the requirements and assign them to the part where they belong. As for the screen you have, it isn't consistent with your description of what a manifest is. What it is is the beginnings of a form to add an item to the manifest. Not the same thing.
Take a stab at it, and post back with your results.
Posted 21 May 2014RemoveItem is a method that removes an item from a list box. It doesn't after doing so become a property that contains the last removed item. You can do as Martyr2 suggests, or you can avoid creating a variable thus:
Combo1.AddItem List1.Text 'You could say List1.List(List1.ListIndex) if you wanted to get melodramatic List1.RemoveItem List1.ListIndex
- Member Title:
- Your Friendly Local Curmudgeon
- 58 years old
- September 15, 1956
- Tullahoma, Tennessee
- IT, Music.
- Forum Leader:
- VB6, VB.NET
- Full Name:
- Bob Rodes
- Years Programming:
- Programming Languages:
- Click here to e-mail me
Showing 50 random friends of 30