[AccessD] Querying user-defined system tables in Acc 2010-2013

[Charlotte Foust]

That's what I tried first.  Same result.  I know back the mdb days you
sometimes had to set the query to run with owner's permissions, but that
went out with workgroup security.  I work with this stuff all the time, but
I don't usually roll out a sort-of security system for clients, and that's
what this is for.

UD = "User-defined", a USys table.



Charlotte Foust
(916) 206-4336

On Sun, Apr 5, 2015 at 6:04 PM, Dan Waters <df.waters at outlook.com> wrote:

> Just as a check, try using "SELECT * FROM [tablename]" instead of your
> variable 'SQLstr'.
>
> Also, what is a UD System Table?
>
> Dan
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Charlotte Foust
> Sent: Sunday, April 05, 2015 7:54 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Querying user-defined system tables in Acc 2010-2013
>
> I'm running into peculiar behavior where attempting to set a recordset
> object from a select * query based on a UD system table runs in the query
> design window but returns no records on db.OpenRecordset(SQLstr,
> dbopensnapshot) in code.  Is it just another piece of my mind drifting
> away,
> or what?
>
>
> Charlotte Foust
> (916) 206-4336
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>