Search results

The ones I've seen come with an endpoint to fetch "now playing" or "popular", they come with pagination parameters, so you can easily browse through them. They also come with endpoints to search by title, year, genre, etc. You don't really need a db for that, because a browser control can simply...

Sorry about that, I merely tried to replicate OP's screenshot the best I could. In a real world scenario, it would probably be better to utilize one of the REST APIs out there and a web browser handles that much better than Access' built-in tools.

I know you're trying to learn, but if you get stuck, this file could help. I'm doing the no-seasons table approach here.

Tabbed docs ftw. 💅 Edit: tabs not relevant

That's my regular LLM experience

Well, the internals of Access are in english and Access is an ancient application that has not received a lot of love by its developers, so I believe it is my obligation to test that kind of thing after the testing done and shown in post 21. I'll check what happens if I change locale.

I changed the application's language to Japanese and Arabic, and I was able to open the FormBotoes.accdb file without any issues the same way I was able to open it using the regular english version and the spanish version. In Post 21, my main point was that I successfully used the arabic file...

These CLI tools turn you into a QA guy, a tester of some sort. It helps tremendously, but that comes with the cost of potentially not knowing what the hell is going on. It might work, but then again, it might do stuff you don't even know it's doing. Then again, you could ask it to do things a...

Any update on this?

Great question, I simply used intelliSense, I recognize the properties of a section object. They look like this. Now, here's another issue I see with Section objects. I switched from english to japanese. This is what shows in intelliSense: (You tell me what it says @KitaYama ) But when you...

Here's what I could find Log Name: OAlerts Source: Microsoft Office 16 Alerts Date: 6/27/2025 9:17:54 PM Event ID: 300 Task Category: None Level: Information Keywords: Classic User: N/A Computer: LAPTOP- Description: Microsoft Access The...

I tried and did it step by step this time. Procedure: 1. Go into the immediate window 2. Type the class name of the form with a problem, followed by a dot to trigger intellisense. The idea is to manually check if there's any element with a weird name. 3. Found 3 elements with weird names. 4. I...

I will try to inspect if there's a solution. I was able to open the arabic file by renaming objects with names written with arabic characters to export and import the form as text. After that, the file worked for me. It's interesting that my samples are causing issues for you, @KitaYama...

I tried, but: Your Excel file has a lot of tabs and it's difficult to understand what you really want to do. You should upload only a tab with the dataset and another with the chart you have problems with. If possible, you should upload an image of what you want to see.

Not sure this is how you should think about it. You should not assume it's reading the internet like a book. It has been trained to respond a certain way based on its parameters, and the responses are always different, which means it's all statistics at play. This is why you should always try...

Whenever I see code I want to use in Access, I adapt it to my style so I can understand it better later. But working with a code sharing tool like this feels different. I see it more like importing APIs for things I don't want to deal with myself. In that sense, I care less about how it was...

@Pat Hartman I'm sorry, but that sounds a lot like a golden hammer, the one size fits all mentality. Forms can be bound or unbound in Access, so that is "THE Access way", by definition.

Absolutely, open source code faces these challenges by default, the important part is that it will let you advance much faster without a lot of bureaucracy and review upfront. That's why it should rely on the feedback of the community. Eventually, the best packages will rise to the top, the bad...

Now that I think about it, it doesn't have to be just for Access. It could cover the entire Office suite and anything else that runs VBA. With help from the Excel community, even though the VBA crowd can be pretty toxic, just like the Access crowd, we'd have a better shot at getting it adopted.

As for how to make it viable, one good starting point would be to reach out to the owners and admins of the different forums and communities where developers already hang out. We could ask for their help to promote the tool and make it visible to as many developers as possible. Even just having...