Good luck.  Implementing a similar solution a couple of times on my
end, I had users export into either a .txt, .csv or xml format.
Interactions with Access in a live online environment isn't the
prettiest thing in the world.

Chad

On 8/11/06, Joel Cass <[EMAIL PROTECTED]> wrote:
>
> Thanks..
>
> Actually the transferring of data part is taken care of.. We have a system
> where public users may want to upload their internal data in access format,
> which is then transferred into a SQL Server database for web use. I want to
> be able to give them the choice of selecting which objects to import, hence
> I need to get a list of available tables.
>
> All the websites on this subject give conflicting information, plus detailed
> documentation doesn't seem to be available from MS.
>
> It's just the "getting a list of tables" part that I need.. And I would
> prefer to use a query.
>
> Joel
>
> -----Original Message-----
> From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED]
> Behalf Of Chad Renando
> Sent: Friday, 11 August 2006 11:10 AM
> To: cfaussie@googlegroups.com
> Subject: [cfaussie] Re: Getting a list of tables in access
>
>
>
> I have had to do this a few times... never did figure out the proper
> way to do it.  It is usually a once-off, and by the time I figured it
> out, I could have done it manually.
>
> I typically just create a Make Table query for each table:
>
> SELECT MyTableTable.* INTO MyNewTable
> FROM MyTable;
>
> and run the lot.  Takes about 30 minutes for 100 tables start to
> finish, including creating the queries.
>
> Chad
>
>
>
>
> On 8/11/06, Joel Cass <[EMAIL PROTECTED]> wrote:
> >
> > The documentation in MS access seems quite vague about this area. I want
> to
> > get a list of tables from an access database to import into our own custom
> > data store. I have fiddled around and have come to the conclusion that
> this
> > is the query that must be run:
> >
> > SELECT MSysObjects.*
> >   FROM MSysObjects
> >  WHERE MSysObjects.Type =1
> >    AND MSysObjects.Flags=0
> >     IN '#accessFilePath#'
> >
> > Can anyone confirm if this is correct? I've tried this on a few various
> > files that I found lying around and have managed to get the same results
> > every time, but you just don't know what may change between versions when
> it
> > comes to MS products (just getting in on the whole debate here..). And
> it's
> > undocumented..
> >
> > Any help is appreciated
> > Joel
> >
> >
> >
> > >
> >
>
>
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cfaussie
-~----------~----~----~----~------~----~------~--~---

Reply via email to