Access application run

Deploy an Access application

Access provides a feature-rich platform for developing database applications. A database application is a computer program that provides both a way to store and manage data and a user interface that follows the logic of business tasks (application logic). This article discusses basic deployment planning, packaging and signing, deploying database applications, and the Access Runtime environment.

What do you want to do?

Plan for deployment

Before you begin, you should ask yourself the following questions about the way that the application will be deployed.

Should the data and the logic be separated?

You can create an Access application that combines data management and application logic in one file. This is the default application structure in Access. Combining data management and application logic in one file provides the simplest deployment method, but this method works best only if a few people use the application at the same time, and it involves some risk. For example, a user could cause data loss by unintentionally deleting or damaging the application file. In most cases, you should separate data management and application logic. This helps improve performance and reliability.

One way to separate data and logic is by using the Access Database command (on the Database Tools tab, in the Move Data group). This command splits your database application into two Access files: one for logic (a front-end) and one for data (a back-end). For example, a database called MySolution.accdb is split into two files called MySolution_fe.accdb and MySolution_be.accdb. You put the back-end database in a shared location, such as a network folder. You distribute the front-end file, one copy for each user, to their computers. You can even distribute different front-end files to different users. For more information, see Split an Access database.

Another way to separate data management and application logic is by using a database server program (such as Microsoft SQL Server) for data management, and Access for application logic. For more information, see Migrate an Access database to SQL Server.

Additional reasons for separating data and logic include the following:

Data integrity and security If you combine data and logic in one file, the data is exposed to the same risks as the application logic. An Access application that uses separate logic and data files can help protect data integrity and security by leveraging NTFS security features on network folders.

Access users must have read, write, create, and delete permissions to the folder where the front-end file is located. However, you can assign different permissions to the front-end file itself. For example, you may want to assign read-only permissions to some users and read/write permissions to other users.

Your application may require further security options, such as the ability to control which users have access to particular data. In this case, you could use SQL Server or SharePoint to store and manage your application data, and use Access to provide the application logic.

Scalability An Access file can have a maximum size of 2 gigabytes (GB). Although 2GB is a substantial amount of text data, it may be insufficient for some applications, particularly applications that store attachments in database records. If you separate the data and the logic, your application can accommodate more data. If you expect that users will store a large volume of data, you might consider using more than one Access data file.

You should also review the Access program specifications for other scalability information. To learn more about Access specifications, see the article Access specifications.

Network capacity If multiple users will need to use the application at the same time over a network, data corruption is more likely to occur if the data and logic are combined in one file. Moreover, if you combine the data and the logic in one Access file, you cannot optimize the network traffic that Access generates. If multiple users will simultaneously use your application over a network, you should separate the data and the logic, either by using two or more Access files, or by using a database server product for data and Access for application logic.

What will the network environment be like?

Choosing the correct Access database solution for your network environment is a critical step to making it successful. Use the following guidelines to help you make the best choice for your needs.

If you only have a few users to share your Access database with, you can use a single database that each person opens and uses on a home network. For more information, see File sharing over a network in Windows 10.

Local Area Network (LAN)

A LAN is an internal network that usually has excellent performance, but is limited to a small geographical area, such as a single room, building, or group of buildings. When you have more than a few users sharing the database on a LAN, it’s best to split the database, store the back-end database in a network folder, and deploy a copy of the front-end database for each user.

Wide Area Network (WAN)

There are many possible configurations for a WAN, which covers an extensive geographical area. You may have multiple offices across a city connected to a public network, a leased line, or even satellites. Often, a Virtual Private Network (VPN) is used for secure remote access from the home or on the road. A simple way to understand a WAN is that whenever you are outside a LAN but connected to it, you are using a WAN.

Warning Avoid using an Access split database in a WAN because performance can be slow and databases may become corrupt.

There are three supported ways to use Access in a WAN:

An Access database with linked tables to SharePoint lists.

A front-end Access database connection to a backend SQL Server database or Azure SQL.

Remote Desktop Services (RDS) (previously know as Terminal Server), which creates a virtual Windows desktop environment on a users’s client computer. RDS has several advantages:

No installation of Access or an Access database is required as users run the Remote Desktop (RD) client which is available on many devices.

Data transfer is minimized between the client and the server because RD is a thin client that efficiently streams just the user interface.

Users can still copy and paste data and print reports locally from the client computer.

RemoteApp can run just a single program such as a turnkey application for vendors or frontline workers.

For more information, see Welcome to Remote Desktop Services.

Will users have Access?

If all of your users will have Access installed on their computers, they can open and use the application as they would any Access database file.

If some or all of your users will not have Access installed on their computers, you can also deploy the Access Runtime software to those users when you deploy your application. For more information, see Understand and download the Access Runtime.

Deploy an Access application

To deploy an Access application, you need to do the following tasks.

Prepare the database as an application solution

To lock down your solution, control navigation and startup, and set other important options, do the following:

Decide how users navigate the user interface: use a default form, create a switchboard, use a navigation form, or use hyperlinks and command buttons.

Decide if you want to customize the Office ribbon and command menus

Apply a consistent Office theme and background

Процедура MS Access Call/Application.Run, сохраненная как переменная, не работает

У меня есть форма MS Access с listbox со списком процедур. Коды процедур хранятся в форме. Там еще есть кнопка. При нажатии на кнопку Я хочу, чтобы она прошла через listbox и выполнила процедуры из выбранных элементов. Я вызываю процедуры, используя Call и Application.Run, но оба метода дают ошибки.

Ошибка компиляции называют: ожидаемый подпрограммы, функции или оффициальный
Application.Run ‘MS Access не может найти процедуру ‘имя процедуры’

2 Ответа

Если вы хотите вызвать sub с помощью Application.Run , вам нужно сохранить его в отдельном стандартном модуле (.бас, нет .cls). Переместите свои подводные лодки в отдельный модуль, и он будет работать.

Ключевое слово Call является устаревшим и не вызывает функцию, основанную на строке.

Форма-это модуль класса , его запущенный экземпляр-это объект : Application.Run не работает с объектами. Если вы хотите вызвать методы объекта, вам нужно использовать CallByName и указать экземпляр объекта, который будет Me . за исключением того, что вы конкретно не можете передать Me непосредственно в CallByName , поэтому вы можете ввести локальную переменную для прокси-вызова:

Или переместите процедуры, которые вы хотите вызвать, в отдельный стандартный модуль, как в ответе Эрика .

Call DoSomething является 100% идентичным DoSomething : первый-это устаревший явный синтаксис вызова, второй-более часто используемый неявный синтаксис вызова . Оба они проверяются во время компиляции, что означает, что выполнение Call NonExistingProcedure вызовет ошибку компиляции точно так же, как вызов NonExistingProcedure .

Похожие вопросы:

В настоящее время я запускаю vbscript в MS Access 2010, который извлекает некоторые вложения из MS Outlook и вставляет эти данные в таблицу в базе данных MS Access. Проблема в том, что я пытаюсь.

Как я могу показать выделенную строку MS-Access listbox? Я использую MS-Access 2007. Я хочу, чтобы первая строка многоколоночного listbox была выделена через VBA. Я пробовал Me.LstSample.Selected(0).

Мне нужно импортировать данные из базы данных MS Access в базу данных SQl Server 2000 один раз в день. Поскольку мне нужно, чтобы это делалось каждый день, есть ли процедура c#, которая могла бы это.

Я пытаюсь запустить хранимую процедуру сервера SQL с помощью кнопки в форме MS Access. Связанный сервер уже создан, но я немного смущен запуском хранимой процедуры из Access. Процедура обновит.

Я написал функцию ms-access в модуле под названием ‘StripLead’. Я сделал однострочную процедуру под названием CallFunction. Теперь, когда я вызываю эту процедуру из ms-access, она отлично работает.

Я только что перенес базу данных MS Access 2003 в MS Access 2007. Но у меня есть некоторые проблемы с событиями. Когда я открыл форму запуска базы данных (MS Access 2003), я обычно могу щелкнуть по.

Я пишу код в VBA, который позволяет добавить нового пользователя в базу данных, используя форму пользователя в MS Excel. База данных должна автоматически обновляться после отправки формы. Я.

У меня есть два модуля. В одном модуле я хочу запустить суб из другого модуля косвенно. По данным MS и множество онлайн ресурсов это должно работать — но это не так. В чем может быть проблема.

Это сводит меня с ума. Используя VBA Access, я пытаюсь настроить набор регрессионного тестирования для приложения базы данных, которое мы разрабатываем. Я хочу пересечь таблицу и вызвать каждый.

Когда я вызываю хранимую процедуру сервера SQL из интерфейса MS Access, используя код, показанный ниже, он перестает работать и выдает ошибку времени выполнения 3146. Эта хранимая процедура работает.

Access application run

М етод Application.Run (доступ)

office 365 dev account |Последнее обновление: 29.09.2017

Метод Run можно использовать для выполнения указанного Microsoft Access или процедуры Function или Sub , определенной пользователем. Variant .

выражение . Запуск (** Процедуру , ** Arg1 , ** Arg2 , ** Arg3 , ** Arg4 , ** Arg5 , ** Arg6 , ** Arg7 , ** Arg8 , ** Arg9 , Arg10 , ** Arg11 , ** Arg12 , ** Arg13 , ** Arg14 , ** Arg15 , ** Arg16 , ** Arg17 , ** Arg18 , ** Arg19 , ** Arg20 , ** Arg21 , ** Arg22 , ** Arg23 , ** Arg24 , ** Arg25 , ** Arg26 , ** Arg27 , ** Arg28 , ** Arg29 , ** Arg30 )

выражение Переменная, которая содержит объект приложения .

Обязательный или необязательный

Имя процедуры Function или Sub для запуска. При вызове процедуры в другой базе данных используйте имя проекта и имя процедуры, разделенных точкой в формате: « имя_проекта . имя процедуры «. При выполнении кода Visual Basic, содержащий метод Run в базе данных библиотеки поиск процедуры в библиотеку базы данных, а затем в текущей базе данных.

Arg1 Arg2. Arg30

Аргументы, которые должны быть переданы в Function или Sub , указанный в аргументе процедуры .

В озвращаемое значение

Этот метод полезен, когда вы управляете Microsoft Access из другого приложения через средство автоматизации, ранее — OLE-автоматизации. Например можно использовать метод запустите из компонента ActiveX для выполнения процедуры Sub , определенным в базе данных Microsoft Access.

Можно задать ссылку на библиотеку типов Microsoft Access из любого другого компонента ActiveX и использовать объекты, методы и свойства, определенные в эту библиотеку в вашем коде. Тем не менее нельзя задать ссылку на отдельной базы данных Microsoft Access из любого приложения, отличного от Microsoft Access.

Например предположим, что определены процедуру с именем NewForm в базе данных с помощью его свойства имя_проекта «WizCode». Процедура NewForm принимает строковый аргумент. В Visual Basic, можно вызвать NewForm следующим образом:

Если другой процедуры с тем же именем могут размещаться в другую базу данных, Указание аргумента процедуры , как показано в предыдущем примере, с именем базы данных, в котором находится нужное процедуры.

Можно также использовать метод Run вызова процедуры в указанной базе данных Microsoft Access из другой базы данных.

Следующий пример запускает процедуры Sub , определенной пользователем в модуле в базе данных Microsoft Access из другого приложения, который выступает в качестве компонента Active X.

Для проверки работы примера, создайте новую базу данных с именем WizCode.mdb и задать его свойство имя_проекта WizCode. Откройте новый модуль в этой базе данных и введите следующий код. Сохраните модуль и закройте базу данных.

Примечание Задайте имя_проекта , выбрав Инструменты, свойства WizCode, в главном меню редактора Visual Basic.

После выполнения этого этапа выполните следующий код из Microsoft Excel или Microsoft Visual Basic. Убедитесь в том, что добавления ссылки на библиотеку типа Microsoft Access щелкните ссылки в меню Сервис и выберите Библиотека объектов Microsoft Access 12.0 в диалоговом окне » ссылки «.

Running VBA Code from a Microsoft Access Macro

Background on Macros

To use combo boxes effectively, learn about the following properties:

There are many Microsoft Access users who are comfortable writing macros to automate tasks but not familiar with module code and its Visual Basic for Applications (VBA) programming language. That’s okay. Everyone has to start somewhere.

The VBA programming language is used across the Microsoft Office products. In addition to Access, you can use it in Excel spreadsheets, Word documents, PowerPoint presentations and Outlook. VBA is also very similar to language used in Visual Basic 6. In fact, the syntax and module editor (Integrated Development Environment or IDE) is practically identical.

In MS Access, macros are completely different from modules. Macros and modules appear as separate objects in the database container:

Macros are structured actions that are easily created by choosing options from drop down lists. After selecting an action, it’s easy to see the available options and choose appropriately.

There’s no need to learn a programming language and it’s very easy to automate tasks such as running queries, printing reports, opening table and forms, etc. Putting a macro in design mode shows the individual commands:

If you name a macro Autoexec, Microsoft Access automatically runs it when your database opens. You can also open Microsoft Access from a command line and specify a macro name after the /x switch to run it when it opens.

For instance, you can run the macro named MyMacro like this:

This assumes the 32-bit version of Access 2016 is located in its default location. To locate Access, use Windows Explorer and search for msaccess.exe.

For a complete list of command line switches visit this Microsoft page on Office Command Lines.

Background on VBA Modules and Procedures

VBA lets you create modules with more advanced functionality than macros. You’ll need to know a little more about programming to write VBA code as it’s not structured like macros since the editor lets you type anything, though Intellisense is available to simplify entering built-in commands. Modules are composed of functions and subs (procedures) which perform the tasks you define. A Function is a procedure that returns a value while a Sub performs its task without returning a value. Procedures can be passed parameters to execute different behavior based on those values.

We have many examples of procedures throughout our web site and our Total Visual SourceBook program is a commercial library with over 3600 procedures. Here are some examples.

Note that Excel doesn’t have macros but often refers to VBA functions are macros.

Running a Function from a Macro

Let’s create a simple function and call it from a macro.

Create a new module

From the Create ribbon, choose Module:

Add a Function

Paste this text into your module. This is a function that shows a message with the current time.

To run it, just put your cursor on the first line and press F5 to see the message box with the current time.

You can also run it from the Immediate Window by pressing Ctrl G to open the Immediate Window and typing:

In our example, the function doesn’t return a value but it still needs to be a Function rather than Sub to be callable from a macro.

To call a function from a macro, it cannot be defined as a Private function. Private procedures are only visible in the module. Without «Private» it is public and visible to other objects including macros. Using Public in our example makes it explicit.

Save the Module

From the menu, select File Save and give it a name:

By default, it’s Module1, but you can rename it.

Run the Function from a Macro

To run this function from a macro, simply add a RunCode action and refer to the function:

Make sure to include the () after the function name. Save the macro. When you run the macro, the function is called.

Run a Total Access Emailer Function from a Macro

Total Access Emailer is our Microsoft Access Emailing program. The add-in version of Total Access Emailer lets you create and run email blasts interactively.

The Professional Version lets you run the email blasts through VBA. The program’s Code Generator lets you easily create functions and set parameters interactively so you can insert it into your projects and invoke it from events such as a button click or other VBA code.

Because it’s a function, you can also run it from a macro. This page illustrates the programmatic interface and the Code Generator which creates a function named RunEmailBlast(). If you paste that into a module and change the first line from Private to Public, you can run it from a macro by calling that function name:

Additionally, you can invoke the Total Access Emailer function, TotalAccessEmailer, directly from RunCode and pass its required parameters.

For instance, this would run email blast 23 with the options specified by the other parameters as defined in the code generator page.

By creating a macro to call that function, every time you run the macro, email blast 23 is run. You can add multiple RunCode commands to run a series of email blasts.

Administering Jira applications Support

Products

Jira Software

Project and issue tracking

Jira Service Desk

Service desk and customer support

Jira Core

Manage any business project

Confluence

Bitbucket

Git code management

Resources

Documentation

Usage and admin help

Community

Answers, support, and inspiration

Suggestions and bugs

Feature suggestions and bug reports

Marketplace

Billing and licensing

Frequently asked questions

Viewport

Confluence

Versions

Licensing and application access

Installing Jira applications

On this page

In this section

Related content

• No related content found

Still need help?

The Atlassian Community is here for you.

To grant users log in access to a Jira application, the application must first be licensed, and secondly, the application must have at least one default group assigned to it. Any users added to this group will be able to log in to the application. This is called application access. Your Jira application may have more than one group assigned to it, and a user may be a member of more than one group assigned to the application, but they will only count as one licensed user for that application. This is covered in more detail on Managing users access to Jira applications.

On this page:

Installing your first application and application access

When you install your first application and license it (you may obtain a license as part of the installation process, or directly from my.atlassian.com), Jira will create two user groups, and add you to both of them. The first group is the jira-administrators group, and this is the group that grants you the Jira Administrator global permission and grants you administrative privileges. The second group created depends on the Jira application you have installed. They are listed below:

Both of these groups are assigned to the application you installed on the Application access page, and the second group is also assigned as the default group. This means any subsequent users you create for the application will be added automatically to this group.

Adding additional Jira applications

You may have a requirement to add another Jira application to your instance. You can install additional applications through your Version & licensing page. This allows you to locate the most up-to-date version of the application and install it. Once installed, you’ll still need to ensure the new application is licensed. Once licensed, Jira will create a default group for the application, but you will not be added to this group automatically. To gain full access to the application, you should add yourself to a group associated with the application.

Running multiple Jira applications

Each Jira application comes complete with a specific set of features and functions, which tailors the experience delivered to its users. Every user in Jira will have access to an application based on their membership of groups. A user may have access to all the applications, or only one application. If a user has access to an application, they will count as a licensed user for that application. For example, if a user belongs to a group for Jira Software and a group for Jira Service Desk, they will count as a licensed user for both Jira Software and Jira Service Desk.

When you have multiple applications installed, by default, all users will be able to view all projects (unless there are specific project permissions set up that prohibit this). This means a Jira Core user will be able to see all Jira Software and Jira Service Desk projects. However, as they are not licensed for these applications, they will not be able to see any features or functions that are specific to that application. For example, a Jira Core user viewing a Jira Software project would be able to see the project and its issues, but would not be able to see any Jira Software specific features, like Agile boards, development information, or release information. These features can only be viewed by a Jira Software user. It’s important to note that Jira Core does not have any specific features or functions that cannot be viewed and/or actioned by other users. This means that if you are a Jira Software or Jira Service Desk user, you can already view and work on a Jira Core project. You do not need to have specific application access for Jira Core, and therefore do not need to consume a license. View the Jira applications and project types overview page for more information on what licensed users can and cannot view and action on projects from other applications.