I am new in VB.NET.I Developed Project in VB Recently.In VB6.0 i worked on ADODB Recordset by Connecting Access DB.And i wrote SQL Queries in the Functions and these Functions Called in the Recordsets. I will send u my code wich i developed in VB6 in the below.
OK, I have this loop I want to perform which involves the serial port. Not to get too specific I'm actually sending data to an external device within a loop The loop involves a Start number, increments by a Step and ends when it gets to Stop This repeats until I click a STOP button.
I understand that there are several ways of Inserting, Updating and Deleting records in a database such as DataAdapters, DataSets, TableAdapters, SqlCommandBuilders, Parameterized SqlCommands, StoredProcedures, etc, etc,etc. According to David Sceppa Sprocs are the most preferred. Ok, I go with him on this one (who am I to challenge him anyway?).
My question is, apart from Sprocs, which of these options is the BEST for a large commercial database application and why, taking performance into account? What are the benefits and drawbacks of each option?
I am writing a program to assist Paramedic students in learning the Drugs that they have to know in order to pass their classes. I have created an Access database to hold all the information on these drugs, but not every student that will use this program will need to learn all the drugs contained within this database.
Right now I have 43 drugs in the database and still growing.
What I want to do is to present to the student the drugs and have them say "Y" or "N" as to whether its on their required list to learn. That way they only work on the ones that they need to.
I've two BGW with similar coding but different approach, My second BGW shows me "NOT RESPONDING" whenever i try move/click/focus to form while the BGW is running.
To write a effecient Active Directory library to ease the work of technicals who are responsible to create access models into the domain controller's Active Directory. This library must allow the following:Basic operations: Add, Modify, Delete, List entries;An entry may either be an organizational unit, group or user (no further need required as of now);I thought about having a class which would represent the domain with which we want to work with.
public class Domain { public Domain(string root) { Root = root;
I have a database with three tables: stock orders order_details
Stock and Orders are self explanatory. Order_details is a lookup table, holding basically just the orderID, stockID and quantity for each item in the order. That's not very friendly for the user however, so what I want to show is a DataGridView with some elements from order_details, and some from stock, i.e.: Part_Code, Item_Name, Description, Quantity, Price
I can create a database view for this easily enough, and bind it to a datagridview. It shows existing items in the order fine, but the problem is the view doesn't update when I add new elements to order_details in the dataset. It appears that it's bound to the main database, and so won't update until I save the record. That also has the problem that it's now much harder to update the database. A simple datagridview bound to order_details would make it easy for the user to enter quantities and for me to save the record, this one now needs a custom update statement.
In summary: - I want to show data from two tables - I want the datagridview editable (well, the quantity column anyway) - I want the datagridview to update when I add entries in the dataset What is the best/easiest way to do this? Is my current approach of a view in the database and custom update statements sensible? How can I get the datagridview to refresh whenever there's a change to the local dataset?
I recently started a project and needed to do some integration with LDAP via DirectoryServices. I've done this in other apps so I went into one of them to see how I did it -- why reinvent the wheel right? Well, while this wheel works, it was developed years ago and kinda smells (it's wooden, firmly attached to the previous vehicle, hard to repair and produces a potentially bumpy ride).So I thought to myself, this is the perfect time to refactor this puppy and make it more portable, reusable, reliable, easier to configure etc. Now that's fine and dandy, but then I started feeling a tad overwhelmed regarding to where to start. Should it be a separate library? How should it be configured? Should it use IoC? DI?
So my [admittedly subjective] question is this -- given a relatively small, but quite useful class like the one below, what is a good approach to refactoring it? What questions do you ask and how do you decide what to implement or not implement? Where do you draw the line regarding configuration flexibility? [Note: Please don't bash this code too much okay? It was written a long time ago and has functioned perfectly well baked into an in house application.]
Public Shared Function AuthenticateUser(ByVal id As String, ByVal password As String) As Boolean Dim path As String = GetUserPath(id)
I'm working on a system where there can be 2 level of users "Admin" or "Researcher".We have the requirement to allow the researcher to change fields for a record a record, but they want the original values to stay in the record and have an admin "accept" or "approve" the changes before the real record gets updated.Has anyone run into this scenario before? I'm trying to think of the best way to do this.
I'm currently working on a system that requires monthly, quarterly and annual reports. I have no problem in generating/retrieving the data, my problem is the presentation. What is the best way to do it? I need the report to be:
I have a wierd problem with threading in an ASP.NET application. For some reason, when I run the code in the request thread, everything works as expected. But when I run it in a separate thread, nothing happens.This is verified by calling the below handler with the three flags "on", "off" and "larma" respectively - in the two first cases everything works, but in the latter nothing happens.[code]
What is the optimal approach to a WithEvents Collection - VB.NET?Have you any remarks on the code bellow (skipping the Nothing verifications)?The problem is when I obtain the LinkedListNode(Of Foo) in a For Each block I can set myNode.Value = something, and here is a handlers leak...
-Could I override the FooCollection's GetEnumerator in this case? -No. :( cause NotInheritable Class LinkedListNode(Of T) Class Foo
I was wondering about what approach to take for writing a state machine or data crunching engine.As such, it wouldn't have any UI component. Since it must be able to talk to other GUI programs, should it be hosted in a DLL? I noticed that there were some State Machine templates for VB but I have no idea how to use them. If any one could provide some pointers to documentation sample code,
now i search for the word basic.if i press the button find. the first "basic must highlighted, and then if i press again the button the next "basic" is the highlighted one and so on.I already finsih that scenario. What i've done is that first im going to search all the positions of the word and then store it in a array. Then after the array populated with different location of the word that is searching. that is the time i call all the indexes of the array one by one. But i don't want my approach because imagine i have 10000 words. and i search for a word or letter. Lets say the result is 5000 match. so it needs my array to be size in 5000. what a mess in memory.
I don't want to used the FinsString or Find function of VB i want some algorithm to do this. Anyone have a easy approach..
How to link my app to an Access database - there seems to be a number of approaches. I can add in my database via the Data Sources tab. Fine if I want to bind controls and view/edit data. But is this the best approach for queries that return an answer that is a different shape to the original table? Alternatively I can connect to the database directly (connection string, etc) and run sql queries. What are advantages/disadvantages of each approach? In terms of flexibility, is the second approach best? Also, does the second approach require the database to be added via the Data Sources tab?
I'm using VB.NET but this question applies to any OO language - Java, C# etc. I've tagged the question with Java and C# but will remove if not considered appropriate. I have an entity class ClassAAA that contains a reference to ClassBBB as one of it's attributes:
Public Class ClassAAA Private Property _blah As ClassBBB = Nothing Private Property _somethingElse As String Private Property _anotherthing As String ' Make it private so cannot instantiate class without supplying ClassBBB ' [Code] .....
I could make the ClassBBB reference public (or supply a public getter method) but that would expose the inner workings of ClassAAA. What I'm thinking of doing is making the ClassBBB reference Friend so that it is only visible in the assembly i.e. a data layer and is not visible to client projects. But this stills feel like I'm exposing the inner workings of the class.
Which is the recommended approach for copying elements from one control to another? Currently I am using something like this: For Each a As Control In control.Controls Controls.Add(a) Next Should I stick to it, or should I change to use the ControlCollection.CopyTo method instead?
I want to know what's the right way to work with objects that belong to a category.I'm building an applications with the following layers:Base data access Data access Business logic + Factories Presentation.I want to pass only objects to the presentation layer and back.I have objects (Employees), that belong to a certain category (EmployeeCat). I was wondering if I should have just an EmployeeCatID property in my Employee class/object, or an EmployeeCat property that contains a complete category object.If I want to fill a GridView with a list of employee objects as datasource, and I used just an ID in my Employee objects, then I will have some work at the presentation level to display the category names, so I think. On the other hand, if the list of employees contains plain category objects... I'm not sure what will happen.
Im writing a small application that need to make up to 300 socket connections at the same time. However i'm pretty confused on how to approach this. My first theory is to have my main thread to manually fire up 300 new threads that each handle all that needs to be done. Another theory is to fire up lets say 10 threads that makes 30 async connections. My last theory is to have my mainthread work with all 300 async connections together with everything else. The question to this is what would be the most effective way to go to save resources and maintain speed.
I am often asked to create a very simple database front-end for friends or family, and the structure of the database (and application) is usually very similar.Right now I am always creating a class that handles all database interactions with some shared functions. For example, there's a function to run a general query and return a table, a function to save/load various items (depending on the application of course). The point is: the code is nearly always the same except for some slight variations.
Here at my company we have an Access application that allows users to create documents based on invoices that are in Great Plains. Documents such as invoices, packing lists, export documentation, etc., etc.This application is very old and very hard to maintain so we're doing a rewrite and I've chosen this project to be my first Visual Basic .NET project.
What is the recommended way in VS.NET to have a global application handler object? Something that can load/verify/return user folders, settings, application specfic settings, manage the unhandled exceptions, etc. I would have a class that has most of the code, then subclass it for each application.
I can create one if I start as a module instead of a form. But then I lose some options such as NetworkAvailabilityChanged, etc. I define a "Public" object from within a form (I don't think so and don't feel this would be the right approach.)?can I "attach" an object to an existing global object store (such as "My."), etc.?
Once created, any object in my application should be able to reference methods/properties of this application object to get default folders, user values, etc. as necessary.
I have a question on the best way to store model data for my app. My app will basically be drawing a bunch of elements (lines) connected to a node at each end. Im trying to decide how im going to store my node data (as well as element data). The node data im trying to store will consist of the node XYZ coordinates and some other info about the node. The element data will consist of the node numbers at each end plus additional info about the element. There a number of ways i've been thinking i can do this. They are:
1) Store my node/element data as a Dictionary object, where the key represents the node/element, and the value would be an array of the information i want to store.
2) Create a "Node" structure and an "Element" structure to store the info i want. Im a bit worried here as my model could potentially have thousands of nodes and elements.
3) Create a "Node" datatable and an "Element" datatable, and store my info in those instead. I can see some advantages in this in regards to displaying information to the user in datagridview etc. But then again i can easily pull the required data from a method i mentioned above, and generate the datatable when required.
Not quite sure what the best approach is. Either way i do it, i will be serializing whatever object i use to save the data to disk.
There exists a database that holds information on each planet in the solar system. The database has multiple tables.The program intends to access this data to display it to the user in a variety of manners. The program does not intend to manipulate the data at its source, though calculations on two fields may be performed to determine certain display characteristics.What is the optimal method for accessing the data?My initial approach, (read: gut feeling, no research) was to take each related row of data from the database and create an object of a custom class based on the data. So you might wind up with:[code]Then use these objects to perform whatever actions the program needed to. I ran into a lot of problems trying to implement this, so that I believe my design approach is fundamentally flawed.
The problem is as follows, a group of users (~50k) must be filtered from a DB, four fields for each user must be saved into a variable, then a second process will take each user and proceed to enable some licences into another system/platform. Both processes will be developed into the same application.
My first attempt was basically a query looping through the users but I wonder if thinking in objects is a better approach.
I was thinking in a structure inside an object to hold the 4 parameters, then pass each user object to the other object however considering the amount of data I'm not sure if this is fine.
I have a program with 3 forms; each has a different role behind them. Form 1 loads when the program executes and the other 2 load by clicking on buttons from form 1. I would like to implement a multithreaded approach where even after clicking on form2 and form 3 I can still execute other form 1 options while form2 and form 3 contents execute. I read through some tutorials and still not to sure how to implement. I figured I need to create instances of the forms 2 and 3 but how to call the threads and control them? I did try a simple one and had some error concerning delegates.