Home | Forums | Contact | Search | Syndication

[login] [create account]   Thursday, April 18, 2024

slxdeveloper.com   Home   Search   Contact us   About slxdeveloper   Syndication  Community   Forums (NEW!)   Newsletter Archive  Members   Your Profile   Submit Article  General   Administration (6)   OLE DB Provider   Miscellaneous (2)  Architect   VBScript (9)   ActiveX Controls (6)   How To's (14)   .NET Extensions (3)  External   OLE DB Provider (12)   SLAPI (SlgxApi.dll)   SalesLogix COM (1)  Web   ASP/ASP.NET (2)   Web Services   Web Client  Downloads   Samples (17)   Documentation (7)   Utilities (18)  Resources   SalesLogix (3)   Programming (1) 4/18/2024 8:15:15 AM slxdeveloper.com Now Live!   View User Profile    User Profile - Timmus Agersea     Timmus Agersea (SalesLogix Business Partner) Customer Systems, Inc fiogf49gjkf0d I worked for SalesLogix (Sage, Best Software, whatever ) for five years and I have been a business partner for two years now (now being May 2006). I am a SalesLogix and Microsoft proponent. I think SalesLogix, SQL Server, and Visual Studio are great products. I also am a musician who betrays his passion by spending time making money on this geek machine. If only capitalism was driven by doing what we want rather than doing what we can . In all honesty, I do enjoy working with technology but I would much rather be on stage. Log in to send this member a message!    Timmus Agersea's Contributions Timmus Agersea has contributed 2 comments and 1 articles.   Select to view: Comments  Articles  Comment: Re: SQL Profile Template fiogf49gjkf0d The SLX Profiler does not capture other applications hitting the database, SQL Triggers, etc. It only captures queries passed through the local machine's SLX OLEDB Provider. If you are trying to track down ALL the statements that are hitting the database you will need to use SQL Profiler. And of course SQL Profiler works on earlier versions :). Timmus Author: Timmus Agersea - 10/17/2006   Comment: You should be able to access forms via their name fiogf49gjkf0d You no longer need to loop through the collection to find your form. You can access it as Ryan has outlined, via the name: Application.Forms("System:Account Detail").txtAccount.Text = "New Account Name" I apologize that I dont know what version it was fixed, but it does work on the current version 6.1.0.1060. Author: Timmus Agersea - 9/9/2003

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.  This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software. code of conduct |

page cache (param): 4/18/2024 8:15:15 AM