Thanks Brendan. I’m not planning on keeping attendance in the database. I will only use the database, at the least the roster layout part, to print a roster.
I may try, as you suggested, adding a field for each date, but putting these fields in a separate “dates” form, so that my student demographic database doesn’t get peppered with dates fields.
I was imagining using javascript to call data and place it meticulously in text boxes on the layout. Hopefully that meticulous work would only have to happen once. But I’m so unfamiliar with javascript, I don’t see that happening.
You are totally right, it is MB, not GB. Sorry for confusion!
My trial period ends tomorrow, so I have to decide whether to stay with Ninox or to go on the migration path to Tap Forms. There are pros and cons for both products. After checking my app statistics on the App Store I found out that I had my first Tap Forms app back in 2011 – boy, that‘s 15 years now. Time is running. In 2021 it was updated to version 5 and currently the Pro version is under observation. So why did I switch to Ninox and FileMaker Pro in between? Honestly – I don’t know. I think the main reason was that these products were used in the company I worked for. And I know there where some issues losing data – which for sure was my fault. Nevertheless I migrated to the other products.
What does mean all this for my decision? Staying with Tap Forms for 1 ½ decade – even if not in the drivers seat – is a strong signal that this app is something great. While switching to the other products I always came back to Tap Forms. The latest experiences with this app told me why. The development takes – a big thank you to Brendan – huge steps, the trashcan will help avoiding loss of data (perhaps regularly backups as well…) and the support is outstanding. Furthermore the community is here to help out or bring new inspirations.
Taking these facts into consideration there is only one solution: I will end the trial period tomorrow but continue with a subscription. There is so much of functionality within Tap Forms waiting to be revealed, so I am really looking forward to continuing this exciting journey.
Thank you all for being part of my decision – and sorry for this long piece of prose but I wanted to share my thoughts with you as you were directly involved.
Hi Cliff,
There isn’t anything yet to do that. That’s a great idea though. I’ll definitely add that to the scripting engine so you can select the Dashboard. And with that you’d be able to run a Shortcut to do that.
Thanks,
Brendan
I love the new Dashboard feature. Will you be updating App Intents so we could create a shortcut that will open a document into the dashboard? Or can this be done now, maybe using a script?
Hello, is there a script that automatically removes members from a membership database when the cancellation date is reached?
Well we still have some time before MacOS 28 arrives :)
The “Lite” version would be the same but with limitations (max. number of records and/or databases for example). So it should not require much separate maintenance. You would make the update on the Pro, and add the limitations to the Lite versions. The objective would be to NOT cannibalize subscriptions of TP Pro, but to add users that would balk at an annual $50 cost (the problem is that it all adds up, and if all software is subscriptions, users will need other define priorities). it could be a one-time cost (Audirvana Origin includes updates for 2 years, then has paid update), or a lower subscription cost, one that could be justified for a lighter use, within the limitations of the “Lite” version…
If you find the right levels, you should be able to ideally get additional revenue. Because users of the Lite version could “upgrade” to the Pro version easily, you would also provide an easy path to further revenue increases.
Just food for thought at this point…
Hi Guardajoias,
Those are good points. Currently I still have Tap Forms 5 on the App Store for people that have older operating system versions. But that will stop working when Apple removes Rosetta from macOS 28. At that point I’ll probably have to remove it from the App Store if Apple doesn’t do it for me (they did for some of my older versions such as Tap Forms 3.5 and Tap Forms 4 (for iOS)).
It’s a difficult decision to make because I’m only just starting to see progress in my proceeds from the subscription to Tap Forms Pro. All last year it was basically the same as when I only had Tap Forms 5 for sale where revenues were declining year after year. But now in the 2nd year, Tap Forms Pro sales are picking up again and renewals are definitely contributing to that. So do I want to cannibalize that? if I build a lite version, do I still have to maintain that with new OS updates and features? Or do I just right to a one-time purchase at maybe 6x the annual cost? Tough decisions.
Thanks,
Brendan
Hi Brendan,
Your reasoning is well understood. The problem is that we all have different uses of Tap Forms (5 or Pro). Some will have a rather intense and/or professional use, and the $50 annual subscription is fully justified. Others like me use TP5 for a single database, rarely used but important. I use it to track a collection of old books. I use BookBuddy for modern books and it is very convenient and complete, but it does not work well for rare/old books, often in multivolume sets etc. For this I use a database I originally designed in Filemaker, then converted to Bento, and perfected in TP5. I do appreciate the relational features, the reporting, and custom displays. So this database is important to me, but it is the only one use, and I am not adding rare books often. So TP5 is perfect as is for me. $50 annually just to keep it going is hard to justify.
So, maybe a solution could similar to what a software company like Audirvana did. They also chose to move to subscription model when they introduced “Audirvana Studio” to replace the music software Audirvana 3.5, for reasons similar to yours. But after a while they introduced a second option: a single-purchase, “Audirvana Origin” that only works for local music libraries, without the access to streaming services included in the “Studio” version only available by subscription. They now have both kinds of customers.
Maybe for “light users” you could have a version that works with a limited number of records and/or a limited number of databases (2 or 3?). This could be single purchase, or a cheaper subscription price, allowing for upgrade by moving to the higher price. $50 is not far from the old price for a single purchase, and half of the Microsoft Office Suite. Again, I understand, and for heavy/Professional users, it makes perfect sense, but you may actually get more users and revenue by offering a “light” version for more occasional users. You would have to see what are the criteria that make sense.
I have script field that outputs markdown. The markdown works correctly.
In another form I have a field that is defined as a Link To Form field. The Link to Form field contains the script field from the other form. The Markdown is not rendered properly. It displays the markdown.
Checkmark Field checked on Universal layout can’t be found in a saved search.
I have a checkmark field on the default layout and a universal layout. I have a saved search that finds all of the records with the checkmark set to true.
If I set the checkmark on the default layout the saved search works correctly. If I set the checkmark on the universal layout it is not registered as true by the saved search. The checkmark shows up on the default layout but the saved search doesn’t register the check. If you uncheck the checkmark and recheck it on the default layout then it works.
I wrote a script to count the records with the checkmark checked and it didn’t see the records that were checked on the universal layout.
I tried a screen layout and it didn’t have this problem.
Hi Brend.
I was thinking about that, but the problem there ist, that you can only joint 1:many. that does not solve my problem, because I need to be able to split billings an there it get complicated, because I can only set one common field criteria. That ist the fun with many to many so that you can select which belongs to wich without self coded criteria. As I said doing it per hand works fine but I wanted to do it via script and that does not seem to word, when noch creating new record :(
Have a nice day
Steve
A Join relationship is the same as a Many to Many except it is managed by a common field in the parent and child forms. Perhaps your script could just populate the common field? Then Tap Forms establishes the relationship for you based on matching values in the matched fields in both forms.
Hi Eric,
It takes a lot of time to keep Tap Forms up-to-date with all the changes that Apple makes to the operating systems year after year. Plus to fix bugs, add new features, and so on. To expect a one-time payment to get the benefits of all of that forever is no longer financially viable for me. Yes, there’s the upgrade model, but as you know, Apple doesn’t support that model in the App Store. I did that once before with Tap Forms 5 by releasing it as a new application with a migration function. Tap Forms Pro is the last time that I have to do that as now I’ll be able to release fixes, new features, and updates to account for OS changes as I go. I won’t have to hold back updates or new features for some big feature upgrade once a year or two. Everyone will now get them as I finish them. Plus I’ve been providing support to all my customers, no matter which version they bought for 18 years now. That also takes time away from development. I love providing help to all my customers. Everyone has always been super nice and I’ve been very grateful for that.
The Rosetta issue is unfortunate. I had fully expected Apple to just keep it there forever. I put a note in the App Store for Tap Forms 5 that it does require Rosetta. It will continue to function forever on Intel Macs of course and anyone who stays at macOS 27 on Apple Silicon Macs. I know that’s not feasible for everyone though. But it is what it is and the decision to remove Rosetta was out of my hands. Tap Forms 5 relies on a database engine that is no longer supported and was compiled for Intel on Mac. In Tap Forms Pro I yanked that out and replaced it with Apple’s CoreData engine and raw SQLite. So that will never be an issue again. Just doing that took me about a year of development.
So I’m very sorry that you’re disappointed in my decision to move to a subscription model, but without having done that, I saw the end of the road for Tap Forms. Revenues were declining year after year and now I’ve finally managed to turn that around. Now Tap Forms Pro has a very bright future ahead of it.
Tap Forms Pro has been out for just over a year now and I’m now starting to see a rise in my income from last year rather than just barely scraping by with a declining income year after year.
I hope you better understand my decision now.
Brendan
Hello everyone,
I have a form called **Rental Claims** which contains a subform called **Bookings**. The Bookings subform is populated by a script that imports transactions from a bank statement file. This part is working well.
When I work manually, I can use the selection dialog in the Bookings subform to view existing booking records and assign them accordingly.
My question is: **How can I perform this assignment via script?**
I cannot simply create the bookings directly in the script because I may need to assign multiple bookings to a single rental claim, or split a single booking across multiple rental claims. Therefore, a **many-to-many relationship** would be ideal, but I have not been able to create these assignments through scripting.
Has anyone done something similar or can point me in the right direction?
Thanks in advance for any information or suggestions.
Steve
Good morning, Brendan.
One of the reasons I chose to use your application—and support a small independent developer rather than a large tech company—was that, years ago, you mentioned that you were not a fan of subscription-based software. I appreciated that philosophy and it was one of the factors that led me to purchase Tap Forms.
So, to my disappointment, I now see that Tap Forms 5 appears to be reaching end-of-life and that the future direction is moving toward a subscription model. Needless to say, I am not particularly happy about this change.
What concerns me even more is that Tap Forms 5 currently relies on Rosetta. As Apple continues to phase out support for Rosetta, there will likely come a point where Tap Forms 5 will no longer run on future versions of macOS. This effectively leaves existing customers with little choice but to move to the new subscription-based version if they want to continue using the software.
Could you clarify the situation? Will Tap Forms 5 continue to be available and supported as a one-time purchase application, while the new version is offered separately as a subscription? Or is the subscription model intended to completely replace Tap Forms 5 once Rosetta is no longer available?
If the latter is the plan, then I will unfortunately need to start looking for alternative software. I understand that subscriptions provide ongoing revenue for development, but personally I am not willing to pay an annual subscription for a personal database application. At roughly $45–50 USD per year, the cost is difficult for me to justify, especially when I originally purchased the software with the expectation of a traditional one-time purchase model.
Thank you for any clarification you can provide.
