Better IDE
- Thread starter jpl458
- Start date
- Local time
- Today, 10:05
- Joined
- Feb 19, 2002
- Messages
- 46,919
Access is Access why would anyone create a custom IDE? The market is not big enough. If you are welded to Jet/ACE as your data store, you can use anything your heart desires as the IDE as long as it supports ODBC Or, just move on if you don't like Access.
MajP
You've got your good things, and you've got mine.
- Local time
- Today, 10:05
- Joined
- May 21, 2018
- Messages
- 9,489
If talking Sql QBE than there are some good third party add-ins.
If talking VBA then most of us use MZTools to give it more functionality.
SQL Editor Add-In Recommendation
Do you use any third party Add-in or application for replacing/enhancing the SQL editor? This has been a long time complaint. Doing just a Web search I see there is quite a bit out there. Anyone have experience or recommendations? Anyone built one? Could be a good group project. Also a year...
www.access-programmers.co.uk
- Local time
- Today, 10:05
- Joined
- Feb 19, 2002
- Messages
- 46,919
Maybe he's talking about the way forms work or using the debugger. The "IDE" is all encompassing
and we got no specific gripe.
and we got no specific gripe.What bugs me the most is getting an error, say in a query, and it doesn't identify exactly what's wrong. It like getting a message, "there's a problem, go find it, I already did". IDE's used with other languages actually highlight the error in the code.
GPGeorge
George Hepworth
- Local time
- Today, 07:05
- Joined
- Nov 25, 2004
- Messages
- 2,856
Perhaps, if error handling is the main problem, you can learn more about handling errors in Access?
For example, do you include error handling code in all of your subs and routines? Do you know how to use Debug.Print? Set Watches? Stop code in Break Mode? All of those things, and more, are available to you in Access VBA, in the IDE. It may not hold our hands like some other programming languages do. On the other hand, it's an older language and that means a lot of the things we take for granted in newer languages do require more effort on the part of the developer.
- Local time
- Today, 10:05
- Joined
- Feb 19, 2002
- Messages
- 46,919
Are you using the QBE to build your queries or are you typing them into VBA strings? You will find that the QBE gives you better error messages than DAO.
- Local time
- Today, 09:05
- Joined
- Feb 28, 2001
- Messages
- 30,050
Given the abstract math model that is the bases for most if not all SQL engines, it is hard as all heck to identify all possible errors. Remember that SQL is set-based, so in theory all SQL operations happen to all records as though they were being affected in parallel. In actual practice, most SQL that directly affects tables doesn't impose an order on the records, so saying "error in record 31" kind of has no meaning. Having said that, I have usually been able to follow the errors in SQL once I learned how SQL looks at things.
Got to also remember this: SQL executes queries one at a time, so there is only one SQL statement to call out in an error anyway. What's wrong? It's whatever you were doing with the single SQL statement you just tried to execute. If you have an SQL parsing error, you get reasonably good errors. If it makes it past parsing and execution plans before it barfs, you have an SQL runtime error and those tend to be cryptic, I'll agree.
- Local time
- Today, 07:05
- Joined
- Oct 29, 2018
- Messages
- 22,506
Hi. I don't have any experience with this, but in case it's relevant to this discussion, I present the following link.
twinBASIC Update: April 24, 2022
Highlights include updated samples for building custom VBIDE tool windows and custom ActiveX controls that you can drop on Access forms and reports.
nolongerset.com
