Tutorial: Publish a Access 2007 database to the web
Access Power Tip: Use the IsClient() expression to conditionally run VBA from Web forms
Play Access Power Tip: Use the IsClient() expression to conditionally run VBA from Web forms
Description
In this episode, Kerry Westphal explains how to use the IsClient() expression to branch your logic depending on whether the form is running in the client or on the Web. In this way, Web forms can take advantage of the client richness, while also bringing the same form to the browser. She walks through an example of how to use the expression to run the client macro SaveAsOutlookContact from a Web form.
For more information check out the Access 2010 Intro series at the Access team blog.
Download
Download this episode
- High Quality WMV (5.6 MB)
- MP3 (1.1 MB)
- Low Quality MP4 (5.0 MB)
- Mid Quality WMV (6.3 MB)
More episodes in this series
The Access Show: Classified ads demo
Related episodes
The Access Show: Restaurant Demo
The Access Show: How the Microsoft Legal Department Uses Access 2010 Web Databases
The Access Show: Classified ads demo
May 2011 Developer Dinner Part 2: Developing SharePoint 2010 Solutions Using External Data…
May 2011 Developer Dinner: Developing SharePoint 2010 Solutions Using External Data and…
Tutorials: Access 2010 Macro Designer
The Access Show: Client performance improvements against SharePoint lists
Using Access 2010 and SharePoint 2010 Services
Tutorial: Publish a Access 2007 database to the web
The Access Show: Access Developer contest - win an Xbox 360, Zune, or Windows 7
The Discussion
-
gbrayut Good video, but next time I suggest moving a little slower and pausing on the important screens so that it is easier to see what is going on.
Keep up the great work!
-
RBear The zip code field in the contacts sample you use does not appear to have the correct property set on it to allow that field to import. This is evident in your video as well. Perhaps you can tell the right people to fix that sample before final version comes out. It can be manualy fixed using an old module posted on the access team blog.
