DataMgr 2.5 Beta 2
What a fun weekend! We got to celebrate my brother-in-law's birthday, I took my girl to a Christmas party, my kids turned 23 months old, and (more relevant to this blog) I finished the second beta of DataMgr 2.5.
So, what is new in DataMgr 2.5 Beta 2 (since Beta 1)?
- Optional "XmlData" argument to "init" method (calls "loadXml" automatically)
- Filters (and named filters) can now accept CF-style operators (like "GTE" for ">=") as well as SQL-style operators.
- Optional "truncate" argument to automatically truncate data to fit in database while saving data.
- Optional "fieldlist" argument to limit the data that can be changed while saving data.
- New methods to return SQL used internally: getSelectSQL, getFromSQL, getWhereSQL. This is very useful with CF_DMQuery.
- New "applyListRelations" method (take tablename,query) for post-calculation of list relations for getRecords() - also useful with CF_DMQuery
- For tables with a simple (single-field) primary keys, the ability to pass a single value into the "data" argument for getRecords() instead of a structure of values.
- New "isDeletable" calculated field available to "getRecords" determines if each record can be deleted based on "onDelete" property of relation fields.
- Verifications on record deletions now check deletes that DataMgr would cascade prior to deleting record.
- New "ftable" attribute (this deserves its own blog entry).
- Some small MS SQL specific improvements
- A few very minor bug fixes
Feel free to download DataMgr 2.5 Beta 2 (zip) or use the repository for the Bleeding Edge Release. For the latest full release, use the DataMgr RIAForge page. DataMgr is open source and free for any use.
I think that one was your idea, was it not? I remember when I heard that suggestion, it struck me as something that should have been there for a long time.
I'm sorry I missed that one. I will try to look into that for the next release.
Your Access database doesn't have appropriate permissions to use tables without loading them via loadXML().
You need to give read permissions for MsysObjects. Last time I looked it was in: "Tools >
Security > User And Group Permissions". I'm given to understand, however, that that might not exist in Access 2007, which might require you to hunt a bit for it.
I don't have Access 2007 or I would look for it myself.
You might try looking at the following as well:
If anyone is having trouble finding this in Access 2007 BTW:
1.Click the little office icon
2. Select Access Options
3. Select Current Database
4. Click Navigation Options
5. Check Show Hidden Objects, and Show System Objects for each grouping option
6.click ok, then ok again
7. Select The Database Tools Tab
8. Click users and permissions
9. select user and group permissions
10. Find the sysobjects tables and give at least read access
Thanks for the kind words and for putting up the instructions for MS Access 2007. I'm sure that will be helpful for the next person to run into that issue.
If so, are there any plans to account for MS SQL's LONGVARCHAR as opposed to TEXT?
It's been about a year and I'm revisiting a project I had planned to use DataMgr on, but without this, I'll have to go another route.
Sorry for taking so long,
Here's a little info that may or may not help you...
For now, to work around the 255 character limit of varchar (in DataMgr), I've commented out line 3629 in 2.5 Beta 2 (Build 166). That lets me continue to use VARCHAR(MAX) fields instead of TEXT for now without too many issues.
Also, you should note that VARCHAR(MAX) fields in MSSQL are reported back as VARCHAR(-1) if I do a table dump using DataMgr. That should help you differentiate them in your code.
I'm available to test anything you need if that will help.
I tried to get out a blog entry announcing 2.5 Beta 3 (with Sean's requested feature) yesterday, but client stuff kept me from it. Hopefully I will get to that soon.
In the meantime, DataMgr is on GitHub now and the code for that release is available there.
Sorry this has taken me so long.