When I press Alt+F11 I get the *'Microsoft Visual Basic for Applications'* and I can start a module. This module seems to be in Visual Basic 6.0. How can I instead write Visual Basic .NET ? Can I do it from the same window?
You are looking at VBA not VB6, though the syntactic differences are small.
VBA is a scripting language for Microsoft applications.
As the comment to your question states, you would need to write a .NET assembly separately and interface with it via VBA.
Difference between Visual Basic 6.0 and VBA
Related
I have been trying to find out if Talend Open Studio has a scripting language. I hope that maybe it would be Perl or Python.
I have been using Microsoft SSIS ETL tool, and they have a Script-Component to handle more complex ETL tasks.
The SSIS Script-Component uses the languages C# and VB.NET as its scripting language.
Does Talend Open Studio have an equivalent to MS-SSIS Scripting Component.
I could not find much on the web on this.
The amount of material available for Talend Open Studio is very little.
Hope someone can shed some light on this.
Talend (Open Studio or Entreprise editions) is built on Java, and enables you to implement complex tasks in Java using tJava, tJavaRow and tJavaFlex components, as well as custom Java routines. You can also build your own custom components using XML to describe components, and javajet to generate the actual Java code.
Earlier versions of Talend (up to version 4) had Perl support, but it's been deprecated.
I'm the new maintainer of an application that was previously done by a contractor. The application was developed using VBA inside an Access project. It consists completely of forms (one of which is opened using autoexec macro) and stuff like click handlers. I don't see any use it makes of Access functionality except for accessing the tables using ODBC table linking done in Access.
These are the reasons I would like to convert this application to a standalone application if possible:
There is no version control at all, just multiple copies of the same project with an incrementing number appended to the filename
The VBA IDE is super annoying
I think the code could then be migrated to more modern languages like C# or VB.net making it more maintainable
Is there any way to convert this to a separate Windows application (I guess using WinForms as that seems to be the same as the forms in VBA) that can be maintained in Visual Studio?
Access for 20 years has supported the standard ‘Microsoft source code control interface. This is outlined in this post:
Version control for VBA file
And this one here:
How to implement version control in Access 2003?
There really little or no reason why Access + VBA, or vb.net can’t be used with source code control. However the SCC add-in that was part of Access was depreciated in 2013. So for versions after 2010, then you can use a script to export the objects. This works quite well – I am using GitHub with Access. So you need a script to export objects now that the SCC add-in is not included in versions beyond 2010 and it works rather well. Access can view each object as "logical" separate. So having all parts in a folder, a zip file, or the Access continuer is moot - don't fall for the physical vs logical concept here that so many people fail to grasp.
•The VBA IDE is super annoying
Hum, never really had much issue with it. I spend good parts of my day using VS2013 and vb.net, but for the most part the VBA IDE is fine for most Access applications. Can you give an example of what feature or something that you find bad with the VBA IDE?
•I think the code could then be migrated to more modern languages like C# or VB.net making it more maintainable
I can’t see why code written in c++, or Pascal or VBA is going to be more or less maintainable? You have to give an example of what you mean here? Maintainable code is maintainable if it is COBOL, Pascal, or VBA.
I guess using WinForms as that seems to be the same as the forms in VBA
No, Access does not use winforms.
Access as a developer tool not really different then say using FoxPro, or say Delphi. Such code and systems can be re-written like any other software development system would require that I am aware of say in the last 30 years of desktop development.
As a general rule, something written in say Delphi, or Access + VBA is not going to by some act of magic is going to be converted to WinForms and .net. That goes for just about any IDE and system I am aware of.
So software in the general computer industry never worked this way in the past, and thus Access is really much the same as most everything else in this regards.
I'm using the C# package of Visual Studio 2010 Express. I want to add an HTML file to my project, but the C# package doesn't seem to have HTML support (e.g. syntax highlighting) included.
I tried installing the Web Developer package hoping it would simply add features to my existing installation. Turned out that they are acting like different programs though. Still no HTML features.
Is there any way to do this?
If all you need to do is edit some HTML and want highlighting, may I suggest a free advanced text editor such as Notepad++ ?
Just would like to make clear, I cannot find straight answer. C# is general specification of this language done by MS, while Visual C# is implementation of this language, again done by MS?
So if we say we develop in C# (in visual studio e.g.) we develop in Visual C# actually.
Is that correct?
Yes, you've pretty much got it. Most of us just refer to it as C# though, since it is after all a Microsoft thing, and their implementation of the language is what most coders use (in Visual Studio).
An example of a C# compiler that is not Visual C# is the Mono compiler. The IDE that uses that compiler is MonoDevelop. Both are not Microsoft products, but do implement the C# programming language (as well as the CLR).
I don't think that "Visual C#" is a particularly commonly used term - C# is the language, so I would probably say that "Visual C#" refers just generally to C# development using the Visual Studio suite of products.
Like I said though it's not a commonly used term any more (and as you have pointed it out it is also a somewhat confusing term).
You can say that Visual C# is the tool that is part of Visual Studio, provided my Microsoft used to create programs in the C# language.
There is the ECMA-334 C# Language specification, that defines the language.
There are other tools to create programs in C#, like SharpDevelop or MonoDevelop.
This whole "visual C#" has caused me much unnecessary grief (including one during an interview , given I had never heard of the term 'visual C#' and apparently the interviewer didn't even know what it was and was just trying to put checkmark beside qualifications). To sum, Visual C# doesn't exist. It's just C#, we should file a petition to remove that stupid qualifier.
Visual C# is the name of compiler (and IDE). C# is the language. It is the same as Borland C++ and C++ (first is the specific compiler). Or MySQL and SQL.
For all the answers that "Visual C# is C# developed in Visual Studio" - I would point out that the C# Compiler (CSC.EXE) is not part of Visual Studio but is delivered as part of the Microsoft .net Framework - which is completely independent of the Microsoft Visual Studio line of development tools.
In that it has any meaning at all (beyond the initial marketing idea that it would appeal to Visual Basic developers, who were the majority of Windows developers on launch day) I'd say it refers to C# compiled by the Microsoft implementation of the .net Framework.
Whether or not Roslyn compiles "Visual C#" or "C#" is anyones guess.
C# is a kind of programming lang, something like Java, Ruby, Python.
Visual C# means Microsoft Visual Studio/C#， it's IDE for programming C#.
u also can write C# code in notepad.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Version control for VBA file
Does any kind of version control exist?
If no, is there any good solution for collective development of MS Access 2007 database with VBA ?
Microsoft have produced a Source Code Control add-in for Access 2010:
Source Code Control add-in allows
integration with Microsoft Visual
SourceSafe or other source code
control systems to allow
check-in/check-out of queries, forms,
reports, macros, modules, and data.
You can also see the differences that
have been made to your checked out
objects.
The only one integrated VC solution for Access is Microsoft Visual Source Safe however it's poor designed and even Microsoft internally avoid from using it ;). Some people call it "Source Destruction System", but I personally know success cases with using it. Generally, it could be a good solution for small and medium projects due to its limitations.
Here is a very critical article about VSS:
http://www.highprogrammer.com/alan/windev/sourcesafe.html
The other option is to design your own code to export VBA solution using Application.SaveAsText() - it's partially undocumented feature of Access API.
I work with an Access application and Team Foundation Server Source Control. You need to switch the source control provider Access expects; I used this tool, Sourcecode Control Switcher, to do so when we moved from VSS to TFS. Once you've switched, you can setup the source control settings in Access and build a source-control-connected .mdb from TFS. It works nicely.