Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In order to do it in the manner you want, you either need to make an instance of the classes as @Chipmunk suggests or make the method Shared. You also should get away from the old VB6 method of doing this. Your method should look like:</p> <pre><code>Public Shared Function Add(ByVal n1 As Int16, ByVal n2 As Int16) As Int16 Return n1 + n2 End Function </code></pre> <p><strong>Edit:</strong><br /> This would then be called using:</p> <pre><code>Dim x as Int16 = MyFunc1.MyFunc2.Add(15, 16) </code></pre> <p>Using <code>Call</code> assumes you are executing a sub and not a function. The purpose of a function is to return data. Simply <code>Call</code>ing it won't result in the desired effect.</p> <p><strong>Edit 2 (example)</strong></p> <p>You can use a module for this as @Chipmunk states, or you can use a class. My preference is class only because MS hasn't made their minds up about modules (they did away with them for one of the versions - I forget which - and then brought them back).</p> <p><strong>Class method</strong></p> <pre><code>Namespace MyFunc1 Public Class MyFunc2 Public Shared Function Add(ByVal n1 As Int16, ByVal n2 As Int16) As Int16 Return n1 + n2 End Function End Class End Namespace </code></pre> <p>Usage in Form1.vb</p> <pre><code>Imports MyFunc1 ... Public Sub DoAdd() Dim x as Int16 = MyFunc2.Add(15, 16) ' MyFunc1 Namespace imported, MyFunc2 ' is assumed. No instance is created End Sub </code></pre> <p><strong>Module Method</strong></p> <pre><code>Public Module MyFunctions ' Notice no shared modifier here. The module uses the legacy module ' concept to assume that it is shared Public Function Add(ByVal n1 as Int16, ByVal n2 as Int16) As Int16 Return n1 + n2 End Function End Module </code></pre> <p>Usage in Form1.vb</p> <p>Since the module would be in a referenced namespace in your project, you would just call it directly:</p> <pre><code>Public Sub DoAdd() Dim x as Int16 = MyFunctions.Add(15, 16) ' This assumes that your MyFunctions ' module is in an imported namespace End Sub </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POVB.NET namespace and class syntax
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJoel Etherton
    1. USJoel Etherton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMillions of hours on vb6. Fairly new to vb.net. What would be the "right" vb.net to do something like this: I just want to make a separate file, with 50 very generic functions, that I can quickly/easily call where ever I need. I thought the "namespace" and "MyFunc.Add()" way *WAS* the correct way to keep things organized (separate file) and avoid conflicts (by using MyFunc.Add) syntax. No?
      singulars
      1. PO
      1. USSusan
    2. COThen if you want to continue VB6 style you might want to stick to Modules. Or are you starting out on Object Oriented Programming?
      singulars
      1. PO
      1. USChipmunk
    3. CO@Susan: Yah, I work with many of the same. While the syntax is the same and some of the paradigms transfer over, so much is different between 6 and .Net (such as Namespaces) that a lot can trip you up. One thing you might try (as an exercise) is removing the `Microsoft.VisualBasic` namespace from your references. This will break any code that has legacy VB6 syntax in it and force you to use all .Net constructs. It will be aggravating at first but will get better with time.
      singulars
      1. PO
      1. USJoel Etherton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload