Data Center & Security
Do you have questions or need help?
Latest Blog Posts
The Recycle Bin provides a safety net when deleting documents, list items, lists, folders and files. When you or site visitors delete any of these items from a Web site, the items are placed in the Recycle Bin.
Items in the Recycle Bin remain there until you decide to permanently delete them from your Web site, or until the items are permanently deleted after a set number of days, which is based on a schedule defined in Central Administration. When you delete an item from a Web site, the item is sent to the site’s Recycle Bin. If you click Recycle Bin on the Quick Launch, you can see all of the items that you’ve deleted from your site. You can either restore or delete the item from the Recycle Bin. When you delete an item from the Recycle Bin, the item is sent to the Site Collection Recycle Bin.
1. End-user deletes the Agenda document from a document library.
2. The document is moved to the Recycle Bin for the site, where people can restore it or delete it.
3. If the file is deleted from the site Recycle Bin, it is sent to the Site Collection Recycle Bin, where an administrator can restore it or delete it permanently.
The Site Collection Recycle Bin gives the administrator of a site collection greater control over deleted items by providing you with a second stage safety net before an item is permanently deleted from a site. By default, a second stage Recycle Bin stores items that you delete from your Recycle Bin. When you delete an item from your Recycle Bin, the item is sent to a second stage Recycle Bin that the administrator of the site collection manages.
The Recycle Bin is enabled in a site collection by default, and is configured in Central Administration at the site collection level. When enabled at this level, the central administrator can specify how long items remain in the Recycle Bin before the items are emptied. The central administrator can also disable the second stage Recycle Bin, or disable the Recycle Bin in a site collection altogether.
As a site collection administrator, you can view and manage deleted items across a site collection from the Site Collection Recycle Bin page. From this page, you can view items that are currently in a user’s Recycle Bin and items that a user has deleted from his or her Recycle Bin (which is the second stage Recycle Bin). Users who delete an item in the Recycle Bin can contact you to restore the item back to its original location as long as the item hasn’t exceeded the original deleted date that the central administrator set. By default, items in the Recycle Bin are deleted automatically after 30 days. Regardless of whether or not an item is sent to the users’ Recycle Bin or to the Site Collection Recycle Bin, items are deleted automatically after the number of days that the central administrator specified.
NOTE: On a site for which the Site Actions menu is customized, point to Site Settings, and then click the settings that you want to view.
NOTE: On a site for which the Site Actions menu is customized, point to Site Settings, and then click the settings that you want to view.
NOTE: When you view items in End user Recycle Bin Items, the items that you delete are sent to Deleted from end user Recycle Bin.
Keep in mind that only the Site Collection administrator can permanently delete all of the files from the Recycle bin and free up the storage space.
Before creating a Login Form, you need to set up a user table that can verify the login ID and password on the Login Form. The step of creating Login Form can be followed below:
Create a table tblSecurity with a SecurityID and SecurityLevel field and add admin for SecurityID =1 and user for SecurityID =2
Create a table tblUser with a UserName, UserLogin, UserSecurity and UserPassword fields. Remember to add an input mask on the password field so that passwords are not blatantly visible in the table.
I choose to display the type of user rather than just the raw number of the User’s security level by using the Lookup options in the design view. This way the UserType field is a number corresponding to the User’s security level because it refers to the SecurityID in the tblSecurity but displays the user’s UserType in text (admin, user etc.). You can create the UserType field from the Lookup Wizard on the dropdown of Data Type column.
Create a Login Form from the Dialog form design. Then customize the form to your liking.
Create two text boxes in the Login Form as txtUserName with label Login Name and txtPassword with label Password
Under the “On Click Event” of the Cancel button, add the Embedded Macro with a QuitAccess command to exit the program or Access application
Create a Navigation and Admin Form area to reroute your users to the appropriate area of your database application.
Under On Click Event of the OK button, add the VBA code below under the Event Procedure
Option Compare Database Private Sub Command1_Click() Dim User As String Dim UserLevel As Integer Dim TempPass As String Dim ID As Integer Dim UserName As String Dim TempID As String If IsNull(Me.txtUserName) Then MsgBox "Please enter UserName", vbInformation, "Username required" Me.txtUserName.SetFocus ElseIf IsNull(Me.txtPassword) Then MsgBox "Please enter Password", vbInformation, "Password required" Me.txtPassword.SetFocus Else If (IsNull(DLookup("UserLogin", "tblUser", "UserLogin = '" & Me.txtUserName.Value & "' And UserPassword = '" & Me.txtPassword.Value & "'"))) Then MsgBox "Invalid Username or Password!" Else TempID = Me.txtUserName.Value UserName = DLookup("[UserName]", "tblUser", "[UserLogin] = '" & Me.txtUserName.Value & "'") UserLevel = DLookup("[UserType]", "tblUser", "[UserLogin] = '" & Me.txtUserName.Value & "'") TempPass = DLookup("[UserPassword]", "tblUser", "[UserLogin] = '" & Me.txtUserName.Value & "'") UserLogin = DLookup("[UserLogin]", "tblUser", "[UserLogin] = '" & Me.txtUserName.Value & "'") DoCmd.Close If (TempPass = "password") Then MsgBox "Please change Password", vbInformation, "New password required" DoCmd.OpenForm "frmUserinfo", , , "[UserLogin] = " & UserLogin Else 'open different form according to user level If UserLevel = 1 Then ' for admin DoCmd.OpenForm "Admin Form" Else DoCmd.OpenForm "Navigation Form" End If End If End If End If End Sub Private Sub Form_Load() Me.txtUserName.SetFocus End Sub
Set the Login Form to display immediately when the Access Database is opened. Go to File->Options and select the Current Database option from the list. Then set the Login Form as the display form.
It should be noted that while this login procedure is helpful to have permissions and different roles withing your Access database and may be needed for our Remote Desktop Hosting – it is not necessary for any hosted Access Web App or Sharepoint Application since you can use the Sharepoint user roles and login procedures rather than handling it within the Access Database itself.
Access 2013 introduced a new way to make a database available in the browser, called the Access Web App. This first article focuses the general features and points for consideration when developing your Access database.
With the release of Access 2013, you can create now create two different types of database applications, the first is the traditional desktop database. This has traditionally been called an Access database and consists of one or more files stored on your computer, network, or remote server with Access or the Access runtime installed so that you can open and operate these databases.
The second type of database application you can create is called a 2013 web app (not to be confused with the Sharepoint 2010 Web Database). These Web Apps can only reside within Sharepoint 2013 Enterprise or newer. They are not created and do not reside on your local computer.
A web app is cleverly designed so that everything is hosted on Access Hosting’s private cloud, so while you are using a desktop copy of Access to work on changing your design, all the changes you make once saved are automatically saved up to our Sharepoint solution. This means that there is no publishing process, but it also means that you can’t easily undo your changes (or mistakes). Keeping a backup of your own work is very important, but Access Hosting also backs up your entire site collection (not just the web app) every night so we can restore your entire site from a major blunder.
Your web app can be placed in your personal folder in Office 365, or created in a Team Site/Subsite. Team Site/Subsites allow for you to both collaborate with other licensed users and what are known as external users. An external user is someone with a FREE Microsoft Online account (easily obtained), and you are allowed between 500/10,000 external users depending on your subscription.
Access Web Apps run in your browser. This is where most of your users will interact with your application. Web Apps do not have the same robust design features as traditional desktop based applications. When designing a web app you will find yourself switching between your installed copy of Access on your desktop computer and the runtime browser window. You’ll have to have Access installed on your computer to make changes and design the Sharepoint Web App, but will often want to reload your browser to see your changes take effect and to visualize the end user experience.
The MS Access interface used to design web apps is very different than the traditional design tool so you will need to spend some time getting used to the new interface. It is relatively simple and offers standard form views and formats to get an Access web app up and running quickly in Sharepoint.
When designing an Access Web App, it helps to forget everything you already know about designing a traditional ms access desktop database application.
Web Apps do not have the customization options and power of a traditional access application (if you have a powerful Access application developed for the desktop, you can look at our Remote Desktop hosting which lets you leave your robust database application or custom software as-is while you move it to our private cloud). Don’t worry though, your ms access database still stores data in tables. In an Access web app, you can easily jump from table to table using the navigation included on the left pane of the browser. Tables can be re-ordered, hidden, have the captions changed and a graphical icon changed. This acts as the primary method of navigating between parts of your application.
You relate your tables together using a lookup. For those familiar with desktop databases then think of a web app lookup as a combination of desktop lookups and table relationships. There is no place in the web app to view all the lookups together, these are managed individually as part of the table design process.
Once tables are linked by lookups, Access will automatically create views of the data which link the data together using the lookups. For example in an order processing system, an order will have a lookup to a list of products in that order. Access will then automatically create a view including a list of related orders for each product.
If you don’t use lookups, then you will miss out Access saving you time by the process creating views of your data automatically. Once you have these different views of your data, you will find that some of them are exceptionally useful for viewing data from a different perspective. If you find something that you don’t like, you can remove it that view from the web app.
When you select a table, then on the top right of the main screen area next to the table selector is the View Selector for the chosen table. Microsoft Access will automatically create a List (Details) View and Datasheet View (Big Excel Sheet). You can then add to, remove, re-order, re-title and change the views.
The default List View comes with a built in search bar feature. By default, your web app will search every field for whatever you type in. Once again, Access does all the hard work for you.
A web app only supports one kind of primary key which is an auto-incrementing number (this is similar to the Autonumber data type found in a traditional desktop database and the Access Web Services 2010 primary key restrictions). The key field will automatically be named ID, but you can rename it.
Access has great features for importing data, but you should note that upgrading a database to a Web App is very much starting from scratch; You can import your data into your web app, but you will have to design all your views, reports, forms, and other functionality from scratch (mainly because web apps can’t do everything that a desktop database can). Before you try an import an existing desktop database, make sure that you change your desktop database so that every table has an autonumber primary key, and every foreign key is a long integer. If you don’t do this then you will run into problems.
Certain legacy data types are not supported, and those fields will not be imported. OLE Objects and Attachments are not supported. Instead there is a new Image data type which supports .gif, .jfif, .jpe, .jpeg, .jpg, or .png formats (notice that the bmp format is not supported).
If you have data in Attachments or OLE Objects, then these will need to be extracted and held outside the database in separate files, the exception is for supported image formats in
The web app data is held in a SQL database on Access Hosting’s servers, these are automatically managed as part of your Subscription and hosting plan. You can create as many web apps as you like with our plan and are only restricted by storage (which can be upgraded at any time).
To program a web app you use macros (VBA is not supported!). There are two different kinds of macros. User Interface macros manage how a user interacts with you application interface. Data macros are used to perform operations on your data.
While Access Web Apps DO NOT support VBA programming or provide a browser based reporting capability, you can use the Access Desktop application to link to your data online to perform more complicated actions. You can quickly and easily connect to your Access Hosting Web App to create reports and more. Check out this tutorial and video on how to use this feature.