 Welcome everyone, this is Eric Frazier from the Marketing Team at FoulMaker and I'm your host for today's FoulMaker Go and Business Web Seminar, giving you a real world look at how Berkeley College of Music and their team are using FoulMaker Go to benefit their organization. Also joining us today is Ryan Rosenberg, Vice President of Marketing and Services at FoulMaker. Before we get started, I'd like to cover just a few housekeeping items. We strongly recommend that you participate in this Web Seminar with at least a broad band connection. If you have any problems or require online assistance at any time, you can contact Citrix Technical Support at 888-259-8414. Again that number is 888-259-8414. On the next slide, I'd like to cover how you guys can answer or ask questions today in the presentation. Go to your control panel and choose the questions area, enter your question and hit submit and we will cover as many questions as time will allow at the end of our presentation. With that, I'd like to introduce Ryan Rosenberg, he's our Vice President of Marketing and Services at FoulMaker and he will briefly talk about the FoulMaker product line, Ryan. Thank you Eric. Yes, I'm delighted to be able to talk to you all today. Thank you for coming to the webinar. First I'd like to give you a brief overview of the FoulMaker product line. The FoulMaker product line consists of clients as well as servers and also an important part that runs on the iPad and iPhone but it all has one main purpose which is to help you to create custom solutions for the iPad, the iPhone, for Windows, Mac and the web. Now I'd like to talk for a minute about the iPad and the iPhone because you're going to be hearing a little more about that later in our case study today so I could just switch to the next slide. To run a FoulMaker solution on the iPad or iPhone you need to download the free FoulMaker Go app from the iTunes App Store. Now the nice thing about this is FoulMaker databases that you create will just work. Even of course the screens will just work to be able to see your information but beyond that you'll be able to get access to the underlying business logic or automation that you put in. For example, scripts that you might implement or the relations that you set up. Even going back to a server and accessing SQL sources will work through the FoulMaker Go interface and of course security is built right in through the FoulMaker Go interface. However, you may not want your databases to just work. You may want to take full advantage of the iPad and iPhone. The good news is FoulMaker Go is definitely designed for that as well. It comes with a full touch interface. That means that controls and menus are customized for the iPad or iPhone and things like gestures being able to double tap for example is supported on the device. Furthermore, you'll be able to take advantage of iOS specific features such as the signature capture or being able to use the camera on your iPad and iPhone to capture images or being able to use location to find out where you are when you capture key data. Now speaking of location, it's quite likely that if you're using an iPad and iPhone you may go on the road. You may be in many different locations. So the good news is that there's a lot of ways to access your central data when you're on an iPad or iPhone. First of all, you can simply open your databases remotely. So if you have a solution on a FoulMaker server, you can use FoulMaker Go on an iPad or iPhone and just connect to that database to be able to see your data run your solution. Alternatively, you can do a simple integration by simply emailing databases out and having people open them remotely, update them and send them back. And there are lots of intermediate steps. Many developers in the sync model where certain records are taken offline, worked on offline and then put back later when they're updated. Many different ways. And of course, given the flexibility of this platform, I think it won't surprise you that there are many different ways in which customers are using FoulMaker to create amazing solutions. Here are just a few examples. For example, you'll see Benetton using FoulMaker to do retail inventory or you'll see FoulMaker helping improve operations on the Austin Convention Center exhibit floor. This is a place where they have giant trade shows and conventions. They need to set up all those booths and run electrical lines and stuff and they manage all that with a custom FoulMaker solution. You'll see organizations, a lot of medical work, where you have secure information being accessed such as patient records while nurses are going around from hospital to hospital. It's not just about larger organizations too. Small businesses use FoulMaker all over the world. So for example, you'll see a sea breeze farm. This is a small farm up in near Seattle, Washington that uses FoulMaker for everything, both managing production of custom cheeses as well as managing a point of sale system for when they sell their goods and services. So FoulMaker is a very flexible platform. You'll see many different uses. If you want to see some of these uses, go up to the FoulMaker website. You'll see lots of case studies. But today we have a real treat for you. A fantastic story about the Berkeley College of Music. And to do that, I want to introduce Damien Bracken, who is from the Berkeley College of Music. Damien was born in Ireland, actually, and he's a graduate of Trinity College in Dublin, where he was awarded a Master of Arts with focus on music competition. Now he has gone on to 27 years of experience in higher education, and currently he's the Dean of Admissions at Berkeley College of Music. By the way, Berkeley is one of the top music schools in the country. In fact, it's one of the top music schools in the world. He's a composer and a pianist, and he has a very broad and diverse experience in the music industry. He's been a performer. He's been a producer and a ranger, a songwriter and a composer. He's also a technology enthusiast, as you will find out in a minute here. And he's innovative in the way he applied his technology. He's a passionate music education professional. He believes in the value of music to society, and he's using FoulMaker to help achieve those ends. So I'd like to now turn this over to Damian Bracken. Thanks so much, Ryan. It's a pleasure to be here to talk about my experience with FoulMaker. Over the last several, I think as many as 28 to 30 years I've been using FoulMaker Pro in my capacity as an administrator at Berkeley College of Music. Let me just give you a little bit of background about Berkeley. It was founded in 1945, and the concept of this school was to break from the classical Western tradition and teach music through the music of the time, which in those days was bebop and jazz music. Most of the studies happening at Berkeley in that day were teaching professional musicians how to arrange for big band, and then they would go out onto the road and get additional gigs as arrangers. But since then, we've expanded greatly into a school that offers as many as 12 different majors, all offering a bachelor's of music degree. We've been studying performance, film scoring, songwriting, jazz composition, music business, music therapy, and many others. While we originally started out in the back bay in Boston, we since then have opened a new campus in Valencia, Spain, offering master's degrees in film scoring, in performance, in business, and we also have an online degree program, Berkeley Online, which offers several certificate programs and individual courses covering a wide range of topics around music composition and performance and production. We are planning to launch our first undergraduate online degree in September 2014, so we're very excited about that. But in terms of our brick and mortar facility, we have more than 9,000 undergraduate and graduate applicants annually, and one of the most important things about how we review our applicants for admission to Berkeley is what's called our audition and interview process. So every applicant to the college is scheduled for an audition and interview at one of more than 150 sites throughout the world. We have teams out on the road constantly auditioning and interviewing, and FileMaker plays a critical role in capturing all of the data that we ultimately use to sit down with the board of admissions and select our class on an annual basis, and you'll be hearing more about that in this presentation. When I first began to oversee the admissions operation at Berkeley College of Music, at the time it was a very manual, paper-driven process, very labor-intensive, as you can imagine, very error-prone. Essentially, we were using hard copy files for every applicant. It was difficult to track application volume and measure the quality of applications coming into the college, and I knew at that point that I needed to come up with a solution that would help us manage the data that we need to capture, do a more effective job of capturing the data in the first place, but also once we've captured the data, tracking it, measuring it, reporting on it, and using it to make good decisions for the future. At the time, our enterprise system was being widely used across the campus, so we took a look at that. We also took a look at products like Microsoft Access. Eventually, I was introduced to FileMaker through someone at the college who, at the time, was the chair of the Music Synthesis Department at Berkeley, and I very quickly was able to leverage FileMaker and begin to use it in a way that was so powerful and meaningful to me that I've never stopped using it ever since, and this is my first use of FileMaker was in 1992. All we were looking at was a product that allowed flexibility, adaptability, that had some advantages in terms of rapid development and deployment across campus, and so we made the decision that we would go with FileMaker to do it. Remember, we were transferring a paper-based process into what is now a fully digitized applicant evaluation and assessment process, and we're housing our data on a secure remote server that we access in order to review our applicants to the college, and for any number of queries we may have in terms of what our applicant pool is looking like. It may be a question of quality in terms of what's the level of our applicant pool. We can report off of that using FileMaker. It might be what's the demographic of our applicant pool, and are we getting what percentage of our students are international? What percentage of our students are guitarists or bass players, et cetera, et cetera. So very quick and easy access to the data on a platform that we essentially customized for our own use, and of course Berkeley is a very specific niche kind of market. We're looking at very particular criteria when we look at students who are applying to join our community, and we're using FileMaker to gather all of that data for us in a very, very comprehensive way. In addition to the audition and interview data, of course, we're capturing the application itself, and we're capturing academic transcripts and other demographic data from the pool. We have a very, at Berkeley it's a fixed application deadline, and our biggest class every year is the fall class, which starts in September. We have three semesters annually, one that begins in September, one that begins in January, and one that begins in May. But fall is by far our biggest pool, and we have an early action deadline of November 1, and then we have a regular, what we call a regular action deadline on January 15. And these students are applying to have a decision released by March 31st. So essentially, we have a very, very tight window to gather the data and review it as a pool. The big advantage to FileMaker and the system that we're using now is, of course, that we're kind of gathering this data as we go. So as we travel throughout the world and audition our applicant pool, that data is coming back to the mainframe, if you will, the central server at the college, and we're able to compile, aggregate, assess the data as we go. So that by the time we finally get into the committee phase of the Board of Admissions sitting down and looking at all of our data, we have a very complete picture of our applicant pool at that point. I'm showing you a kind of a quick sketch of the current system that we use in terms of data and where the data is coming from. So in addition to FileMaker, which is, FileMaker is being primarily used to capture all of the assessment and evaluative data on the applicant. We also have an online application that's a SQL-based application. And that application syncs to FileMaker on an hourly basis so that we can see applications as they come in. And then of course, we also have an enterprise system and we are looking at data from the enterprise system also in terms of application status and things like that to give us the complete picture on the student. So we're not running this system purely using FileMaker data only. We're using multiple sources and that's something that FileMaker has been very easy to adapt to in terms of linking to these various data sources. It's a big advantage for us in the current system that we use. I think I mentioned earlier the first deployment of FileMaker was in 1992. And since then, it's quite a large sophisticated group of files. It's really the backbone of the data that we use to evaluate and assess students for admission. Not just for admission, but also for scholarship consideration. And also we have quite a large student employment program that has run almost exclusively through FileMaker in terms of matching students to positions and positions to students, etc. Here's a quick view of a screen that we would see on campus when we're at home and logging into the server. So this main screen showing is an audition evaluation screen. We're assessing students on a variety of areas in terms of their musicianship. Up at the top, there's some summary data in terms of where the student is from and overall kinds of ratings in terms of the quality of the student. This is a Korean student that auditioned with us when we visited Hamamatsu, Japan in February this year, and a very strong musician. If you look in the blue area, you'll see that there's a number of tabs. And each of these tabs houses detailed information on various aspects of the student's application background, communication history. We log every communication with a prospect and applicant so that we can review that history as we go. Some of our students will attend summer programs or shorter programs that we post when we travel on the road. And all of that data is captured so that we can see it in the student's history. And then we have various tabs here that are more specific to a function. So a tab for applicant advisors, a tab for the board of admissions, a tab for counseling, et cetera. So lots of different data coming together here in the workplace. Here's a screenshot of the interview layout that is used, the detailed layout for interviewing a student when we're trying to determine their fit for the college and ours to them. And here's our on the road database. This is when we travel, as you can see, this was for Hamamatsu in Japan, the trip that I mentioned earlier. So we're data entering into this database and that data comes back to our central system. So on a nightly basis, what we're doing is submitting this data to our auditions coordinators at the college. We have two dedicated personnel whose job it is to schedule and capture the data, upload it back into the exported out for on the road when our teams are traveling and then bring it back into the server for use by the board of admissions after all of the auditions and interviews have been complete. And this is just a typical iPad window, login window where we would go to open up one of these on the road databases. So the delivery of FileMaker Go, as I mentioned to you, I've been a user of FileMaker ever since 1992. And I'll never forget the day actually that one of my tech people at Berkeley emailed me the link to FileMaker Go. I downloaded it on my iPad. I launched it and opened up our database on the server. And I was working like instantly. And it was so exciting. I was using layouts that we had built in our desktop product and really having no issues at all. This is an interesting point about moving from the system that we built in-house and then taking that system on the road with us when we travel using our iPad. We've done very little to virtually no customization of those databases in terms of the layouts. We're able to open up the database and use it instantly on the iPad just as we would if we were logging in from a desktop and going to the server. So it's instant. You can take a solution that you've built in-house and instantly have users accessing it through FileMaker Go on the iPad, which is another big advantage. This screen just talks a little bit about what I've been referencing in terms of how we sync the data back to the server. So there's 150 sites in excess of 150 sites around the world. We're traveling to Asia, Latin America, all over the US, all over Europe. And having these audition and interview events capturing the data on the road and then uploading all of that data back into the central server for review by the Board of Admissions during that critical month of March when we're making decisions on who our entering class will be for the upcoming fall semester in September. This slide is talking about some of the advantages that I feel I clearly get from being a FileMaker user. You can imagine how labor-intensive the admissions process was prior to the digitization and capturing of all of this data. And there's no question in my mind that I would need a much larger staff than what I have now to get all of this work done. We have a huge volume of applications coming in. They're coming in online. They're being synced almost immediately with our FileMaker system. And then we have very sophisticated scripts that are built to schedule every applicant into an available slot. And we're very customer-oriented, so we ask our applicants to give us their first choice for audition site and their second choice for audition site. I would say 80% of the time we're able to meet first or second choice. If not, we're going to invite you to our campus in Boston or in Valencia, Spain. But the system is built in such a way as it runs through the first choice and if a slot is available, it assigns you that slot and sends you an invitation to audition an interview at that time and in that location that you requested. You know, I mentioned, I think briefly before the live reporting, this is something that's very powerful, particularly for my team. We're all traveling almost constantly on the road and need to be in touch with the data from no matter where we are. So literally at the push of a button, I can log in to FileMaker Go on my iPad and I can look at data on the server and make important decisions around how we're shaping our class, what the quality of the applicant pool looks like, and any number of inquiries that we might have at that time in terms of what the demographics of our applicant pool looks like. And this is something that I'm monitoring almost on a daily basis. And again, FileMaker gives me that quick and easy access to that data in custom screens that we built specifically for that purpose. So it's very user friendly. The other important thing about FileMaker Go and using it on the iPhone and iPad is, you know, we have, for instance, in Boston, where about 50% of our applicants will audition. On any given Saturday from November through March, we are welcoming as many as 300 students to our campus to do their audition and interview at Berkeley. It's a very intensive kind of day for those students. It's a very important day in their lives. Many of them are applying to their first choice school. They want to go to Berkeley. It's Berkeley or bust for many of these kids. So it's very important for us that we have a very high touch, high quality experience for our applicants. So when they show up at Berkeley, they're greeted at the door by a student ambassador holding an iPad, using FileMaker, and checking that student in as they arrive at the reception desk, which makes for a very warm, welcoming kind of feeling for that student and their family. And then when it's time for that student to go to warm up before their audition, that same FileMaker system will display that student's name on a giant screen that's in our waiting area so that they can see, oh, it's my time to go and warm up, and they're escorted by a student ambassador to their warm-up room. So very high-end, very user-friendly, gives a very, very high sense of professionalism for these audition and interview events. So going forward with FileMaker, we continue to see FileMaker as being a central part of our toolkit at Berkeley in terms of the application process to the college. We can see opportunities for further integration with our CRM, so we're going to be focusing on that in the upcoming year. And with the ever-increasing number of applicants from throughout the world and the pressure that that puts on my team and our audition and interview process, we're looking at options to do online auditions and interviews and thinking about ways that we can integrate our FileMaker system with the online audition and interviews so that there is easy access to the online meeting even as we document the audition and interview in FileMaker and feeding that data directly to our server. So those are the two areas of focus for us in the upcoming year, leveraging FileMaker. You know, we continue to be both impressed and relieved at how robust FileMaker is for Berkeley College of Music. It's really, I can't imagine that we would be where we are today without having leveraged FileMaker in the ways that we have. And it's certainly meeting, it's helping us meet all of our annual goals and the challenges that we put ahead of us. It's a core product for Berkeley, and we look forward to continuing to leverage FileMaker technology as we develop our application process at Berkeley. So that's the end of the presentation portion. I'd like to pass it back over to Ryan for a Q&A session. Very inspiring. I'd like to just remind everyone that now is a great time to enter in your questions for Ryan and Danyin to address. Remember all you have to do is click in the control panel, enter in your question and hit send. And why don't we go to the last slide and take a look at some of the FileMaker resources. Of course, you can download FileMaker Go for iPad or for iPhone for free from the iTunes Store. And we also have a lot of free FileMaker Go resources available on the website, you know, information about how to set up your databases, white papers, video tutorials, and we even have lots of other Web seminars related to FileMaker Go and mobile devices. And with that, I'd like to hand it over to Ryan for the Q&A. Thank you, and thanks to you Danyin. We've got lots of questions here, but let me start, Danyin, by just having you step through the process in a little more detail, how it works, where the information is moved, kind of gathered together, moved from a server out to people in that, because this is a lot of questions around that. So, from my understanding, what happens is that you've got a bunch of systems, SQL-type systems, and you're pulling information from those systems, as well as I imagine entering some information directly into FileMaker, and then you have a central database in a server, correct? And then you somehow extract information out of that and email it out to your folks that are going on the road. How does that exactly work? Yeah, so it's all scripted, so we're not necessarily pulling data from SQL, we're viewing it live. When it's time for an audition team to go out on the road, an audition team is made up of two faculty members that run the audition, a board of admissions member who's running the interview portion of the day, and typically there's two student ambassadors or student alumni who are helping meet and greet the students and get them to their warm-up, et cetera. But the data is simply an extract from our server, so it's grabbing some of the demographic data that resides in the SQL database. It's grabbing the audition schedule information in FileMaker, and it's downloading it to a local file that's then emailed to the team, and they take it out on the road. On a nightly basis, they'll send a copy of that database back to the auditions coordinators who then upload that information and update it in the server. So it's actually, I mean, it's quite simple. I mean, obviously we had to write the scripting to make sure that the correct data was being exported in the correct fashion. But it's gotten to the point now where it's simply you lost the script, the file is emailed to the team leader, and then the file is sent back to the auditions coordinators as soon as they're done with it. And that way you can have information available each night. Correct. Yeah, and we're looking at this information on a daily basis. Do you feel, here's a question about, okay, you're gathering a lot of this information together, do you feel the need to archive past year's records or do you just prefer to have them accessible all the time? How are you handling the data over time? We keep five years of records in our suite. So we'll archive anything that's past five years, but we do have all of that data accessible to us if we need to get to it. I had a couple of questions related to, you know, the troubles of traveling on the road. I mean, you go on the road a lot, so I'm sure you understand this. What happens if, oh, I don't know, someone were to lose an iPad, haven't forbid, and do you have a way of sending the data back out? How do you handle that situation? Has that ever come up? I don't think anybody's ever lost an iPad, but I'm sure it's possible. It can happen. I mean, you know, obviously everything is password protected and not only the device itself, all Berkeley laptops and iPads and any Berkeley-owned device is password protected. Every database that we set out on the road is password protected, so we're not, you know, we've never had an incident that has caused an issue for us in that regard. We have backups of everything. So, you know, if you're doing, of course the great thing about FileMaker is that it saves your data as you go. So, you know, it's been many, many years since we started doing this, and we've been very, very fortunate. We've never had any major data break. One of the questions, a lot of questions about how the mobile process works again, how large are your databases on your mobile devices? Has this been a problem for you? And someone's also asking about the sync process. So is it taking you a long time to email these databases out and get them back, or is that a pretty quick process overall? No, they're very manageable size files. You know, on a, when we're traveling on the road, it's like 30 people a day. It's typically what we schedule, which is a very full day of auditions and interviews. You're always talking a few hundred records. 90 records, you know, it's nothing. These are small files. Someone wants to know about your use of tagging to help categorize the students for future searches. I was looking in your screen there, and you have a lot of different ratings and things. Is there any sort of a tagging process you're using as you're entering the information that helps kind of categorize the information? Yeah, absolutely. I mean, there's standard, in the business, what you would call enrollment management rating systems. You know, we're looking at various aspects of the applicant. There's no question that at Berkeley, the most, the driving force, as I'm sure is true with many other colleges, is the quality of that applicant. So in addition to the audition and interview, what's the quality of their academic record, you know, and what other accomplishments and achievements have they mentioned in their application? I had another question here, again, about how you were doing this in-house. It says, do you have an in-house tech managing and development and maintenance of your databases? So I guess in general, they're asking, how do you develop and maintain your databases? Who is doing what parts of the development and maintenance? Yeah, I have, in the admissions office at Berkeley, we have two web developers that are responsible for file maker maintenance, as well as development of online forms and other web products, web-based products that we would use. So yeah, this is, as you can imagine, it's a crucial core piece of the business. And it's critical that we have people in-house. And when I say in-house, I mean in the office of admissions, not in our IT department, although our IT department will support us as necessary, obviously, but, you know, it's critical, using a system like this, that you have expertise on the ground that can address any issues that might come up on a daily basis and or tweak things as we go. If we see an opportunity to improve the database, in some way, we can do it right there and then. Yeah, that's one of the neat things about file makers that you can bring a consultant to do heavy work, but it's still, you have the ability to make those quick changes. I should mention, Eric, you know, that we have used for larger projects, like for instance, scheduling all these thousands of auditions and interviews. We brought in a team called the Support Group. They're local here in Boston. And so they've been a tremendous help. So, you know, we will definitely, when needed, bring in outside consulting to develop the product. I have a couple of questions here that I'll take here. One of them is, can we use the forms that are already built in FileMaker Pro on the iPad? Yes, you can. When FileMaker has a number of what are called starter solutions included, and these are, you could think of them as templates, there may be a little more advanced than just a typical simple template. They have scripts and things associated with them, but then they have a bunch of different screens and they're for different tasks that you might find important, such as managing project or managing inventory. And all of those starter solutions have screens built in there for the iPad or iPhone. So, whether you use those screens or not, they're a good way to learn how those screens ought to look and furthermore, they're a good starting point if you wanna use those and build out from there. Another question is, can we view FileMaker data from a web browser? There are a number of ways to do it. One way is what's called instant web publishing, which comes off of FileMaker where it's generating the web pages for you, so you publish a screen. It'll take a screen that you have, generate web pages. You'll probably wanna adjust that screen, probably build a layout as it's called or a screen or a form for the browser, but you can publish information that way. And there's also custom web publishing. I'm curious to know, and that's where you build using coding techniques like PHP and you connect to FileMaker. Damien, have you done any work integrating the web with FileMaker in any of your process? Yeah, actually, oh man, now I'm trying to remember what year this was, but as early as the late 90s, I was using FileMaker and Lasso to develop an online application for, at that time, what was called the World Scholarship Tour. So people would log in online and submit applications using FileMaker and that's a long time ago. We're not using FileMaker right now at Berkeley for web-based applications, but it's certainly not ruled out by any means. So I imagine today that the applications flow through web interface into a SQL database and then from there, the data flows into FileMaker as appropriate, is that how that works? That's exactly right. Okay, that's great. Here's a question and this is a hard one to answer, I don't know, I'll try winging it at you because you've been working with FileMaker for so long, but what was the biggest challenging in implementing FileMaker? Any parts of it, was there a challenge of, let's say, connecting to SQL or was there a challenge in building up your screens? Where would you say if you were new to FileMaker, you might wanna, the extra challenge would be? Um, you know, I think like any other product, FileMaker has its kind of quirks about it. So I think you need to put the time in up front, especially if you're a new user with FileMaker to take advantage of the online courses of which there are many, take advantage of the FileMaker website itself because it's a fantastic resource. And, but stick to it because I can tell you that, you know, I've had a lot of exposure to a lot of different kinds of technology and FileMaker can do so much more. I would say that, you know, at Berkeley, we're really pushing the envelope with FileMaker. We're using it for some very, very sophisticated kinds of processes that are really, you know, critical to the school, but it's well able to manage them. You just need to, and you know, the other thing that I learned down the road is don't be shy about bringing in a consultant when you know, when you need to. I think it's, there's a lot of good FileMaker consulting out there. We're very fortunate to have the support group here in Boston, they've been a great help to Berkeley. And, you know, at Berkeley, often things are on, you know, we have a limited window of time to accomplish tasks in terms of FileMaker development. So, you know, if something is really significant, we'll bring in some additional help to do that. It's not that we couldn't do it ourselves, it's just that, you know, we're like everybody else, we want it yesterday. We don't want to have to wait to have it. Well, we just have time for a few more questions. Here's one, how are your new employees being trained how to use FileMaker? You built the system, what do you have to do to train someone to use it? Well, Berkeley has a, my staff in particular have a kind of an onboarding process that walks all new staff through the systems and, you know, even beyond FileMaker, you know, what it is to be in that particular role that they may have been hired to fill. But FileMaker is certainly a core component for every one of my staff at Berkeley. And like I mentioned before, we have two technical people that can sit down and do more technically oriented training for folks. And then we have something that we call, you know, a shadow system, or you will sit down with an experienced staff member and walk through the processes and learn the system that way. And is most of the learning how to use FileMaker isn't more learning what the process itself is typically? We don't, you know, we've built our system in such a way as that very few people who work for me actually know how to use FileMaker. You know, they're using it on a daily basis, but we try to make that as transparent to them as possible. That's the goal, isn't it? Make it as simple as possible. So they're just using it. Yeah, exactly, yeah. So they're just accessing data. You know, they give us great feedback because they'll talk about data flow and field views and things like that that we can then address. And I have the level of expertise to address those issues as they come up. But we just try to make it as simple for them to access the data as they possibly can because then they become more productive. I just got time. We'll just do two more questions. I've got one I'll answer and then I'll pass one more to you. A person asked me about publishing on the web. I had mentioned that earlier. And asked, could it be, if you publish on the web, are you required to publish all your information or can you limit it? And you have a lot of control over that. In FileMaker in general, you can set up views or screens that are read-only. You can set up ones where people can update information. You can set it by different people having different, get access to information. That same sort of thing applies on the web. You can have a browser, a screen that, you could just read information and you can't even enter anything into it. Or you can limit it in many different ways. So FileMaker is very flexible in that fashion. One of the questions that people wanted to know about was how long did it take you to move your solution to the iPad? Did you have a lot of development to do or were you just able to run it right away? No, that was the beauty of it. I literally, when FileMaker Go came out, I downloaded it. I was in my kitchen at home, I remember, because it was a big moment for me. I downloaded FileMaker Go and logged into the server at Berkeley and off I went. I was using the exact same layouts and interfacing in the way that I normally would. So that's the, what we currently don't have at Berkeley is a customized iPad version of our data. We're simply accessing the database in the way that you would on your desktop. But it was, I mean, there was literally no development work switching from the desktop to the iPad. It was just another device, another means of accessing the data. That's fantastic. And in many cases, people want to develop a custom screen for the iPad and you can and you should. But in your particular case, it's working for you. So no, no, no, no, no issue. Well, I believe you're very disappointed in the fact that I haven't done that. So why are they disappointed? Because they just want a different screen or they just the concept of it or? Yeah, I'm saying some of our listeners today. Oh, some of your listeners. Customize it. But we have, it does work very well for us. I'm sure we could make it prettier and make it a little bit slicker, but we haven't gotten there yet. Well, I think the main goal is, and what we strive for at FoundMaker is to provide flexibility. I mean, that's one of the hallmarks of FoundMaker. If you want to do custom development on the iPad or iPhone, we're there, we have starter solutions, we have training. You don't, you don't have to. I'd like to mention one last thing here for everyone, which is people ask, where can I learn more about FoundMaker? Again, there's a lot of good resources on the FoundMaker website. One thing you might want to be aware of is something called the Technical Network or TechNet. It's a free program that anyone can sign up to on the FoundMaker website. And it gives the person, if you sign up for it, you'll have access to a whole bunch of information, a custom form just for people developing in FoundMaker. There, you'll have access to all these files and training materials. There's also a site on the FoundMaker website that covers training. So if you wanted to get some training, you wanted to take, learn by video, or you wanted to go to a class or buy a book. There's a whole bunch of content up there on where you can get training and how to get it. So there's a lot of different ways to learn FoundMaker. And if you get started now, maybe you'll be like Damien and still be getting a lot of value out of FoundMaker what, 20, 30 years on. So Damien, again, really appreciate your time today. You're doing some great work there at Berkeley and you're making great use of FoundMaker. And as you say, you're using it to help bring more music to the world. And I think that's a great goal and you're achieving it. Yeah, and thanks to FoundMaker. It's been a great resource. Okay.