access-macgyver
New member
- Local time
- Today, 03:35
- Joined
- Nov 17, 2016
- Messages
- 3
Hi Everybody! Somewhat newbie to databases in general. I understand them conceptually, have a pretty solid technical understanding of common web languages, but unfortunately not a great understanding of database languages. I also have a very strong sense of UX, know what I want in my head, but sometimes need help with solutions to execute my vision. That said, I am primarily here for help in building/adding on to an access web app database. I have been able to macguyver almost every part of it through googling, testing, googling, testing, combining ideas and more. But as the Access web app is limited and water downed compared to the full desktop program, there are a few things I **think** can be done but haven't been able to find help on that either explicitly give me the solutions I am looking for OR explicitly say it can't be done...with a legitimate explanation. There have been a handful of things that I read in several places couldn't be done, only to figure out through further research that with the right approach, that was not the case and actually found either a straightforward solution, work around, or alternative. Many of those solutions came from reading this forum! More or less, in addition to ongoing support/kick around ideas, I have come to this forum with my bucket list of sorts to either get answers, or lay them to rest. Thanks in advance!