- About Us
- Guidelines & Policies
- Guidelines
- Backup Guidelines for Departmental Computers
- BearID Guidelines
- Confidentiality Guidelines for ITS and Library Employees
- eCommerce Guidelines
- Disposition and Certification Guidelines for University-Owned Technology Equipment
- E-mail Guidelines
- Fiscal Year-End Deadlines
- Hardware Support Guidelines
- Information Access Forms
- Information Release Guidelines
- ITS Outage Procedures
- ITS Procedures
- Loaner Equipment Guidelines
- Mobile Device Guidelines
- Proper Use of the Loaner Program Equipment Guidelines
- Responsible Use of Electronic Resources
- Standards
- Technology Purchasing Guidelines
- University ID Card Photo Usage Guidelines
- Workstation Configuration Guidelines
- Policies
- Guidelines
- Networking & Telephone
- Resources & Systems
- Advancement Systems
- Arts & Sciences Technology Center
- Baylor Box Service
- Baylor OsoMobile
- Bearhaus
- BearQuest
- Browser Information
- Canvas
- Casey Computer Center
- Classroom Technology Services
- Cloud Technology Services
- Computing Facilities
- Crystal Reports
- Custom Application Development
- Financial Systems
- Forms Library
- Gartner Resources
- Human Resources Systems
- ID Card System
- Personally-owned Computer Repair Service
- Institutional Research & Testing
- Requests for Technology Systems & Software
- ResTech
- Student Related Systems
- Technology for Faculty
- Technology for Online Students
- Technology for Retirees
- Technology for Students
- Website Support
- Security
- BearAware Bulletins/Alerts
- April 2011 BearAware Bulletin
- July 2011 BearAware Bulletin
- January 2012 BearAware Bulletin
- April 2012 BearAware Security Alert (Faculty)
- March 2013 BearAware Alert
- July 2013 BearAware Alert
- September 2013 BearAware Bulletin
- March 2014 Security Alert
- Fall 2015 BearAware Bulletin
- December 2015 Bulletin
- April 2016 BearAware Security Alert
- September 2016 BearAware Security Alert
- November 2016 BearAware Bulletin (Students)
- November 2016 BearAware Bulletin (Faculty/Staff)
- April 2017 BearAware Security Alert
- Fall 2018 BearAware Cybersecurity Update
- BearAware Cybersecurity Alert: September 13, 2018
- Account Request and Approval
- Automatic Updates/Patches
- Baylor IDs
- myBearID
- Duo Two-Factor Authentication
- Baylor University's InCommon POP
- BearAware
- ID Card Information
- Identity Finder
- Information Security Program Plan
- ITS Badge Information
- Microsoft Advanced Threat Protection (ATP)
- Policies
- Safe Computing
- Server Registration
- Virus Protection
- VPN
- Web Filtering
- BearAware Bulletins/Alerts
- Services
- AppCenter
- Code42 (formerly CrashPlan)
- Departmental Request for Purchase of Non-Standard Technology
- Digital Signage
- Disposition
- Getting Help
- Hardware
- Installation Services
- Inventory Reports
- Ivanti (LANDESK) Information
- Leaving Campus
- Loaner Program
- Printing On Campus
- Quick Search
- Self Service Help
- Software
- Technology Purchasing
- Training
- Trouble Ticket
Filemaker Pro
| Vendor | FileMaker |
| Description | FileMaker Pro is a cross-platform database application from FileMaker Inc. (a subsidiary of Apple Inc.), known for its combination of power and ease of use. It is also noted for the integration of the database engine with its GUI-based interface, which allows users to modify the database by dragging new elements into the layouts/screens/forms that provide the user interface. This results in a "quasi-object" development environment of a kind that is still largely unique in the "industrial strength" database world. (Descriptions from https://en.wikipedia.org/wiki/FileMaker_Pro) |
Special Dependencies |
n/a |
Eligibility |
Faculty/Staff |
Where is it available? |
Windows - AppCenter (Software Installer for Campus Computers) requires IE. |
Platform |
Version |
Windows Mac |
16
16 |
Support:
Level A - Baylor Standard
During normal business hours, the Help Desk is available to respond immediately to questions on the currently supported version of software. If the Help Desk is unable to answer the question, a Heat ticket will be recorded and sent to the second-tier response team. Software at this level is supported by several individuals responsible and every attempt will be made to respond to the ticket in a timely fashion.