Up until recently, my LINQ-to-Sage provider didn't support projections, so the client code had to explicitly "transfer" to LINQ-to-Objects, like this:
var vendorCodes = context.Vendors.ToList().Select(e => e.Code);
Now, with a bit of help from Stack Overflow, I was able to modify my IQueryPr...
var vendors = context.Vendors.Select(e => new { e.Code, e.Name });
and it does I-don't-know-how-many API calls in the background
these CR posts might actually get me into eventual trouble, should my boss decide he wants to package it and sell it
but hey, now it's peer reviewed code
and all he asked me to do was to interface purchase orders from the old system into Sage300. I couldn't believe I had to write all that redundant annoying code, so I made myself a LINQ provider, and now my code looks like it's running off Entity Framework :)
Unfortunately I didn't have access to the API at all (or even the software). I had to reverse engineer it from only the data tables. Talk about needing meaningful identifier names...
Private Function GatherData(ByVal SatAddress As String, ByVal ApptAddress As String, ByRef Clinics As ProcessClinic) As Collection
'@Folder("SatisfactionSurvey.CollectData")
Dim CI As ClinicItem
Have I done it correctly? "SatisfactionSurvey" is my project name.
until I see it in action, I guess I'm unconvinced of the full usefulness of it. Maybe my project just isn't big enough or I've not subdivided into enough modules.
it's 5pm. it's Friday, and I'm ready to go home. I'd be more than happy to pick this up on Monday and do me some learnin'. I might even swing by over the weekend...
> @ckuhn203 I understand the excerpt in the same way. If that's the case, obviously a bit of documentation would handle the problem, at least in the short term.
I don't have time to give it a try today, but I've added @ckuhn203 @Vogel612 and @retailcoder as contributors to the private repo I setup for debugging this issue; if one of you has time to try things out, please by all means go ahead. Otherwise I should have some time early next week.
> Looks like Windows didn't paint it, possibly because it was busy doing something else. No idea why, but I've had this sporadically with many programs.
Morning all. Just a brief glance to see what's evolved over this chilly day as I am going shopping to Costco. Yes, we have one now setup here. Getting to see what digital ears I could find as I am getting an upgrade hardware wise.
> I had to remove the MZ-Tools add-in to get inspection to work. Then reinstalled MZ-Tools and inspection is OK. Who's on first? https://www.youtube.com/watch?v=kTcRRaXV-fg
> Interesting.. this is the first time we have reports of (what appears to be) interactions between the two addins. Which versions are you running (for both)?
@Mat'sMug Hmmm, I had never used the priority buttons before... Looking at the API, there is no way to change the order of References in VbProject.References. The only thing I can think of is to remove references and add them back in the desired order. I'm not really liking that idea.
> I had MZ-Tools installed then installed Rubberduck. Running inspection in Rubberduck did not work. I unloaded MZ-Tools, closed Access, open again and then Rubberduck inspection worked. Reinstall MZ-Tools and then they are both working.
> I had MZ-Tools installed then installed Rubberduck. Running inspection in Rubberduck did not work. I unloaded MZ-Tools, closed Access, open again and then Rubberduck inspection worked. Reinstall MZ-Tools and then they are both working. MZ-Tools (3.0.1212) and latest Rubberduck (2.0.4.19949)
Up until recently, my LINQ-to-Sage provider didn't support projections, so the client code had to explicitly "transfer" to LINQ-to-Objects, like this:
var vendorCodes = context.Vendors.ToList().Select(e => e.Code);
Now, with a bit of help from Stack Overflow, I was able to modify my IQueryPr...
VBA Rubberducking
VBA Rubberducking