Re: MDE-File
- From: Morten <Morten@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 8 Jul 2005 04:20:03 -0700
Dear Chris
When I make my run-time version it consists of:
A main database
Several databases with data – links are made to the main database when
installing
I have made a profile and there is a password. The main database is made in
a .mde file without access to codes etc.
In the main database there are a number a tables that are not linked. Those
tables can via the Word mail merge become visible and it is possible to draw
out data. This can be done without use of password, you only have to open the
data source and the tables will appear.
It is not possible to see the tables that are linked during installation. I
use a code for this:
Set tdfLinked = dbsCurrent.CreateTableDef(Tabelnavn)
tdfLinked.Connect = ";dataBase=" & tabelsti & ";pwd=kkkkkkkk"
tdfLinked.SourceTableName = Tabelnavn
dbsCurrent.TableDefs.Append tdfLinked
tdfLinked.Attributes = dbHiddenObject
Before making the run-time version I have chosen Properties and then Hidden
in order to hide the not-linked tables. When installing it also runs a code
to hide these tables – both things do not help. It is still possible to get
data via the Word mail merge by opening my fff.mde file.
I hope the question makes sense this time.
Looking forward to hearing from you.
Regards, Morten
"Chris Mills" wrote:
> It is not very clear (to me) what exactly the question is you are asking.
>
> I had the same trouble with your previous post ("Merge Word"), so I did not
> respond.
>
> Although I appreciate English may not be your first language, could you
> perhaps post some precise questions?
>
> > I have office develop 2002.
> Good. I do too
>
> > When I install the runtime-version, the user will
> All the ways an application works, should be the same for full Access as well
> as Runtime. And they should be the same for mdb as mde, which is quite
> different from Runtime or not. Of course, some things will run in Full Access
> and not in Runtime. Or some things may run in mdb's but not in mde's. It is
> not clear to me, or at least from your phrasing, whether you "just" have a
> problem with runtime (or mde), or whether you are asking something else.
>
> > The user cannot see all the linked tables...
> > refresh the link...
> This appears to be your main issue. Linked tables and refreshing links has
> nothing whatever to do with runtime or mde. (except of course, for runtime or
> mde you have to do it in code)
>
> I have never heard of "cannot see all the linked tables". If there is just one
> back-end database, then either all the tables are available or not, for that
> location. There could be different security on different tables, making some
> of them unavailable I suppose, but you didn't post it as a security problem.
>
> So I'm not really sure what you're asking. Please forgive me. Can you try and
> post it another way. If necessary, just one single question at a time.
>
> (For a start, say you have everything working fine in Full Access/mdb, before
> bringing in TWO more complications (runtime, and mde) )
>
> HTH
> Chris
>
> "Morten" <Morten@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:42055432-B991-4BCE-93EF-AF6B21D53195@xxxxxxxxxxxxxxxx
> > I have office develop 2002.
> > When I install the runtime-version, the user will
> > be able to merge all the tables in the main file (.MDE) without password.
> > The user cannot see all the linked tables. When I install the program I
> > refresh the link and use dbHiddenObject to hidden IT. This works but not
> when
> > it tries to do it to the other tables.
> >
> > Can anybody help- please:-)
> >
> > Morten
> >
>
>
>
.
- Follow-Ups:
- Re: MDE-File
- From: Chris Mills
- Re: MDE-File
- From: Paul Overway
- Re: MDE-File
- References:
- MDE-File
- From: Morten
- Re: MDE-File
- From: Chris Mills
- MDE-File
- Prev by Date: Re: Need help with code and query.
- Next by Date: Installation problem - requires WindowsNT4.0 service pack 6
- Previous by thread: Re: MDE-File
- Next by thread: Re: MDE-File
- Index(es):
Relevant Pages
|
