WebData Pro Tutorials: Frequently Asked Questions

Questions:

  1. What is WebData Pro? [Answer]
  2. How long will by WebData Pro database(s) remain available? Can I use my WebData pro database(s) as evidence in my ePortfolio? [Answer]
  3. I've completed the WebData Pro sign-up form, and I received my account information via email, however when I try accessing WebData Pro, I am unable to get past the first login prompt. I'm certain that I'm entering my email address and password correctly. [Answer]
  4. I've created a user account for a team mate using "Manage Members", and I have given them their login information, however they are unable to access WebData Pro. [Answer]
  5. I've created a user account for a team mate using "Manage Members", and I have granted them privileges to add records. However, when they attempt to add a record, they receive the following error: "The record could not be added for the following reason(s): Date Added is a required field." [Answer]
  6. I am using the "list" display type for a field, but when I try to edit the field, my changes are not saved. [Answer]
  7. When I try to add a record, I receive the following error: "The primary key, group_id, may not be blank". [Answer]
  8. When I edit an existing field, the Field Name prompt is not pre-populated with the existing field name. Instead it is either blank or is populated with a "0" or contains the word "undefined". [Answer]

Answers:

  1. What is WebData Pro?

    WebData Pro is a Web-based database management system which allows users to create and manage their databases using a Web-browser. It also provides the ability to create a Web-based search/query page, which allows others to query your database. You may also selectively grant record management privileges to others, for instance if you need to allow another classmate or group to add records to your database as part of the evaluation process. WebData Pro will be used in all LIBR 202 classes as of Fall 2012.

  2. How long will by WebData Pro database(s) remain available? Can I use my WebData pro database(s) as evidence in my ePortfolio?

    While we will attempt to keep your WebData Pro databases available for as long as possible, we cannot guarantee indefinite availability. Depending on how long you take to complete your coursework, your WebData Pro database(s) may or may not still be available by the time you reach LIBR 289 ePortfolio. Because of this, we strongly recommend that you document your WebData Pro projects BEFORE the end of the semester in which you are taking LIBR 202. You may document your WebData Pro projects using screenshots or screencasts, which you can then retain for use as evidence for your ePortfolio. For example, you could use the free Jing screencasting service to create a 5-minute walkthrough which highlights your database (table) structure and field definitions, your records, your search layout pages, etc.

  3. I've completed the WebData Pro sign-up form, and I received my account information via email, however when I try accessing WebData Pro, I am unable to get past the first login prompt. I'm certain that I'm entering my email address and password correctly.

    Most commonly this occurs if you included a special character in your password when you completed the WebData Pro sign-up form. Although we're not 100% sure why, occasionally the inclusion of one or more special characters in the password will cause authentication issues. We are continuing to investigate the situation, but in the meantime we recommend that you avoid including any special characters in your password when completing the WebData Pro sign-up form. If you did include one or more special characters, and you are now unable to access your WebData Pro instance using the original password that you chose, then please submit a report using the WebData Pro Tech Support Form.

  4. I've created a user account for a teammate using "Manage Members", and I have given them their login information, however they are unable to access WebData Pro.

    This issue can be due to one of several factors:

    • Occasionally the use of special characters in passwords has caused login issues. We would recommend that when you create an account using Manage Members, avoid including special characters in the user's password.
    • When creating an account for someone else using Manage Members, if you are copying their email address from some other source (a document, an email message, etc), make sure that you do not inadvertently copy over leading or trailing white spaces. If you inadvertently copy over a leading or trailing white space as part of the user's email address, then that will lead to authentication failures.
    • When using the Manage Members tool to add a new member, any upper-case characters in the email address are converted to lower-case characters when the member is added. As a result, at the initial login prompt, the new user needs to make sure and enter their email address as all lower-case. If they inadvertently enter their email address with upper-case characters, the login will fail. Note that the actual situation is a little more complex: The User Name field for the initial login prompt is case sensitive, but the User Name field for the WebData Pro login page is not case-sensitive. But for the sake of simplicity, it's easiest if users just remember to enter their email address completely in lower-case.
  5. I've created a user account for a teammate using "Manage Members", and I have granted them privileges to add records. However, when they attempt to add a record, they receive the following error: "The record could not be added for the following reason(s): Date Added is a required field."

    When using the Manage Members tool to grant record management privileges, DO NOT select the "Limit to 1 Record" option. If you accidentally select that option, the user will be unable to add records and will instead receive the above error message.

  6. I am using the "list" display type for a field, but when I try to edit the field, my changes are not saved.

    When editing a field that uses the "list" display type, you will be prompted to:

    • "Enter the maximum number of characters"

    Unfortunately, it looks like the maximum characters prompt does not pre-populate with the current value. Instead, the prompt is blank (no pre-populated value), and if you leave it blank, the record update will silently fail.

    So, when editing a "list" field, when you reach the maximum characters prompt, you do need to enter a value. Don't leave it blank or else the record update will fail. If you're not sure what to enter for maximum characters, then just use the current value that is defined under the Data Type column for that field. For instance, if the field is defined as "varchar(15)", then you can go ahead and enter 15 for the maximum number of characters. Or, of course, you can increase or decrease that number as desired.

    Also, this problem only seems to occur with fields that use the "list" display type. When editing a "list" field, you need to make sure and enter a value when prompted for maximum number of characters. If you inadvertently leave it blank, then the record update will silently fail.

  7. When I try to add a record, I receive the following error: "The primary key, group_id, may not be blank".

    This problem occurs if you have edited the "_id" field and have inadvertently set the Autocount option to "No". The Autocount option always needs to be set to Yes for the "_id" field (or whichever field you use as your primary key). In general, we don't recommend that students edit the "_id" field, but if you do so, please make sure that Autocount remains set to Yes. If you inadvertently set Autocount to No for the field that is functioning as your primary key, you will receive the above error message whenever you attempt to add a record

  8. When I edit an existing field, the Field Name prompt is not pre-populated with the existing field name. Instead it is either blank or is populated with a "0" or contains the word "undefined".

    We are aware of this issue. It most frequently happens when you include a field named "length" in your table. For some reason, the inclusion of a "length" field can cause some odd issues that can also impact other fields in the table. This appears to be a software bug. We have reported the bug to the software author and we will continue to investigate the issue. In the meantime, the best workaround is to enter the correct field name when prompted. For instance:

    • If you are editing a field named "length", and the Field Name prompt is pre-populated with a "0", then remove the "0" and replace it with "length".
    • If you are editing a field named "color", and the Field Name prompt is blank (no pre-populated value), then enter "color" into the blank prompt.
    • If you are editing a field named "size", and the Field Name is pre-populated with the word "undefined", then remove "undefined" and replace it with "size".

    If you run into other seemingly related issues, then please submit the WebData Pro Tech Support Form.



A SCHOOL WITHIN THE COLLEGE OF APPLIED SCIENCES AND ARTS