Add New Record Issue

I have a form “frm_NewDevice” that has a data source of “tbl_Inventory”.

When I enter all the information and press the save button, which includes the following code:

Private Sub btn_Save_Click()

If Me.Dirty Then

If Status.Value = 3 Then

Select Case cbo_DeviceType.Value

Case 1

GoTo Message

Case 4

GoTo Message

Case 5

GoTo Message

Case 9

GoTo Message

Case 15

GoTo Message

Case 19

GoTo Message

Case 20

GoTo Message

Case Else

GoTo Proceed

End Select

Else

GoTo Proceed

End If

End If

Message:

If AssetTag = Null Then

MsgBox "This device type requires an Asset Tag. Please add one to continue.", vbOKOnly, "Missing Asset Tag"

GoTo Leave

Else

Me.Dirty = False

GoTo Proceed

End If

Leave:

Exit Sub

Proceed:

If Me.NewRecord Then

Call AuditChanges("DeviceID", "New")

Else

Call AuditChanges("DeviceID", "Edit")

End If

DoCmd.OpenForm "frm_Home"

DoCmd.Close acForm, "frm_NewDevice"

End Sub

However, the code runs without issue. No errors, etc. The tbl_AuditTrail gets a new record added as it sees there is a new record in play. The tbl_Inventory is never updated to reflect the new record being added. What an I missing that this is now not working?

submitted by /u/VooDeux48
[link] [comments]

Posted on

Add New Record Issue

I have a form “frm_NewDevice” that has a data source of “tbl_Inventory”.

When I enter all the information and press the save button, which includes the following code:

Private Sub btn_Save_Click()

If Me.Dirty Then

If Status.Value = 3 Then

Select Case cbo_DeviceType.Value

Case 1

GoTo Message

Case 4

GoTo Message

Case 5

GoTo Message

Case 9

GoTo Message

Case 15

GoTo Message

Case 19

GoTo Message

Case 20

GoTo Message

Case Else

GoTo Proceed

End Select

Else

GoTo Proceed

End If

End If

Message:

If AssetTag = Null Then

MsgBox "This device type requires an Asset Tag. Please add one to continue.", vbOKOnly, "Missing Asset Tag"

GoTo Leave

Else

Me.Dirty = False

GoTo Proceed

End If

Leave:

Exit Sub

Proceed:

If Me.NewRecord Then

Call AuditChanges("DeviceID", "New")

Else

Call AuditChanges("DeviceID", "Edit")

End If

DoCmd.OpenForm "frm_Home"

DoCmd.Close acForm, "frm_NewDevice"

End Sub

However, the code runs without issue. No errors, etc. The tbl_AuditTrail gets a new record added as it sees there is a new record in play. The tbl_Inventory is never updated to reflect the new record being added. What an I missing that this is now not working?

submitted by /u/VooDeux48
[link] [comments]

Posted on

Accessibility Updates in Access

Over the past year, our engineers have been working hard towards meeting the Office accessibility standards outlined in this 2016 accessibility roadmap. We have been focused on creating an accessible experience for two user scenarios:

·         Creating and consuming content inside of the database

·         Navigating through the application and database

Here are some improvements which are available now to all Office 365 subscribers:

Table screen reader improvements

The basis of Access, tables, received several bug fixes and improvements to properly communicate information out to the user. Through Narrator, the built-in screen reader in Windows, information about the row, column, data type, and value will now be narrated out to the user. We’ve verified that when focus is on each of the different data types in table datasheet view, the appropriate information is read by Narrator. These accessibility improvements will allow users to better understand the structure of the table and the data contained within it.

1.png

 

Navigating through forms using the F6 keyboard shortcut

 

Forms contain different sections such as the header, detail, and footer and each section can contain separate controls. We’ve added new functionality to Access to allow a user to quickly move focus to the first control inside of the next form section. By using the F6 keyboard shortcut, for example, a user can move from the header section directly into the first item in the detail section. Additionally, subforms nested within any section will also have access to this functionality once focus is moved into the subform.

2.png

 

  

Form functionality and narration improvements

End users of Access databases interact mainly through forms so we’ve made improvements to the keyboard functionality of all controls on forms. We’ve verified that keyboard interactions with all controls on forms provides a better accessibility experience and that the appropriate control information is read by Narrator.

High contrast and visual improvements

For database users with vision impairments, such as cataracts or color blindness, Microsoft Office and Microsoft Windows have made platform improvements to help users interact with data and commands in Access with less eye strain. When users enable high contrast mode in Windows, they can see text more visibly against a contrasting background with different colors for links and disabled text.

For users with high resolution monitors we’ve have improved the rendering for high DPI settings to take more advantage of the pixel real estate. User interface surfaces will have higher DPI and won’t shrink to small sizes.

For database developers

The Access team created a design guide for developers to help make their databases more accessible for their end users. This design guide provides advice and tips on designing a database that is accessible for all and includes specific examples for developers creating Access applications. You can find this guide here .

Ways for you to get more information

Are you responsible for ensuring that the software products your organization develops or purchases meet accessibility requirements? You can find more useful information about accessibility in the Access Voluntary Product Accessibility Templates on this page: US Section 508 VPATs.

Do you have suggestions for how we can further improve accessibility within Access? Please send them to our user voice.


 

Posted on

Trigger code to every front end when back end table is updated

I have multiples front end and 1 back end (All on Access).

I would like to run code on every front end when a back end table is updated.

I’ve been thinking for hours how to do it without success …

The all point is to run a requery on a form when data is updated, so the users will get real time value without F5.

Does anyone have a way to do this ?

submitted by /u/vinceska
[link] [comments]

Posted on

Trigger code to every front end when back end table is updated

I have multiples front end and 1 back end (All on Access).

I would like to run code on every front end when a back end table is updated.

I’ve been thinking for hours how to do it without success …

The all point is to run a requery on a form when data is updated, so the users will get real time value without F5.

Does anyone have a way to do this ?

submitted by /u/vinceska
[link] [comments]

Posted on

Accessibility Updates in Access

Over the past year, our engineers have been working hard towards meeting the Office accessibility standards outlined in this 2016 accessibility roadmap. We have been focused on creating an accessible experience for two user scenarios:

·         Creating and consuming content inside of the database

·         Navigating through the application and database

Here are some improvements which are available now to all Office 365 subscribers:

Table screen reader improvements

The basis of Access, tables, received several bug fixes and improvements to properly communicate information out to the user. Through Narrator, the built-in screen reader in Windows, information about the row, column, data type, and value will now be narrated out to the user. We’ve verified that when focus is on each of the different data types in table datasheet view, the appropriate information is read by Narrator. These accessibility improvements will allow users to better understand the structure of the table and the data contained within it.

1.png

 

Navigating through forms using the F6 keyboard shortcut

 

Forms contain different sections such as the header, detail, and footer and each section can contain separate controls. We’ve added new functionality to Access to allow a user to quickly move focus to the first control inside of the next form section. By using the F6 keyboard shortcut, for example, a user can move from the header section directly into the first item in the detail section. Additionally, subforms nested within any section will also have access to this functionality once focus is moved into the subform.

2.png

 

  

Form functionality and narration improvements

End users of Access databases interact mainly through forms so we’ve made improvements to the keyboard functionality of all controls on forms. We’ve verified that keyboard interactions with all controls on forms provides a better accessibility experience and that the appropriate control information is read by Narrator.

High contrast and visual improvements

For database users with vision impairments, such as cataracts or color blindness, Microsoft Office and Microsoft Windows have made platform improvements to help users interact with data and commands in Access with less eye strain. When users enable high contrast mode in Windows, they can see text more visibly against a contrasting background with different colors for links and disabled text.

For users with high resolution monitors we’ve have improved the rendering for high DPI settings to take more advantage of the pixel real estate. User interface surfaces will have higher DPI and won’t shrink to small sizes.

For database developers

The Access team created a design guide for developers to help make their databases more accessible for their end users. This design guide provides advice and tips on designing a database that is accessible for all and includes specific examples for developers creating Access applications. You can find this guide here .

Ways for you to get more information

Are you responsible for ensuring that the software products your organization develops or purchases meet accessibility requirements? You can find more useful information about accessibility in the Access Voluntary Product Accessibility Templates on this page: US Section 508 VPATs.

Do you have suggestions for how we can further improve accessibility within Access? Please send them to our user voice.


 

Posted on

Customer Story – “A future for children” (ZUKI)

Today’s post was written by Karl Donaubauer, Microsoft Access MVP

 

ZUKIlogo.gif Imagine life as a child living and sleeping on the streets of Kolkata, hungry and barefoot, searching for trash to sell and begging to stay alive. This is reality for thousands of children today, and their future options are unimaginable.

 

 The Austrian charity ZUKI (abbreviation of “Zukunft fur Kinder,” or “A future for children”) has a clear mission: to support the India-based non-profit organization “Missionaries of the Word”, founded in 1998 by Xavier Raj Arul, a local hero who has dedicated his life to helping the children of Kolkata.

 

Thanks to the generosity of many long-time donors, ZUKI and Xavier are providing children with a secure bed, three meals a day, a pair of real shoes, a school uniform, education and professional training.

 

Since its founding in 2002, ZUKI has provided support for over 1100 children – providing them shelter in dedicated homes and sending them to schools in Kolkata and Sundarbans. ZUKI has also been able to open a day center for severely disabled children and run school classes for additional children still living on the streets.

This kind of work relies on appraising, social media, and transparent fund management, all efforts that require efficient and reliable data management. ZUKI volunteers and staff need to track a vast amount of information relating to the children they help, as well as sponsor details and the complex relationship between the two groups.

As ZUKI’s projects and administrative workload grew, they reached out to me asking me to provide technical consultation and build an environment that will support ZUKI’s evolving needs around managing and sharing data. Being an expert in Microsoft products and a long time Microsoft Access MVP (Most Valuable Professional), I built a solution based on Microsoft products and services that addressed ZUKI’s needs and kept costs to a minimum.

Microsoft provides ZUKI with the right technology at no cost. As an officially recognized charity (sealed by the government of Austria), ZUKI qualifies for the Office 365 Nonprofit plan, which provides us SharePoint Online and other tools for free. As ZUKI grows and continues to do great things, cost of management remains around one percent which is crucial for our credibility and success in fundraising.

 

To accomplish this remarkabe efficiency, ZUKI uses a Microsoft Access database application that provides them with a user interface to easily work with their data. ZUKI uses SharePoint Online as a backend for data storage, which lets us collaborate and work against the most up-to-date data.

 

ZUKI_05_Access_UI_Form_Donors_Details.jpg Microsoft Access Form – Donor’s Details

 

Using Access as a frontend and SharePoint Online as backend also supports cases where we need to work offline, as Access caches information until we regain internet connectivity. Additionally, Access integration with Microsoft Excel is a great advantage for us, as we use Excel for additional reporting and data entry in the field.
We are proud that the cost of running this solution is almost zero for ZUKI. Our donors can be sure that all their money is used for those free places and the future of children in India.

Related links:

ZUKI website

ZUKI on Facebook

Microsoft Office 365 plans for nonprofits

 

About the authorKarl_Donaubauer_2.jpg

 Karl Donaubauer is a database developer, consultant, author, conference organizer and speaker based in Vienna, Austria. He works for clients in several European countries, runs the most popular Access website in Europe and has been a Microsoft Access MVP since 1998.

 

Posted on