[AccessD] Dialog Box for Creating .txt tables

Hewson, Jim JHewson at nciinc.com
Thu Mar 19 09:33:35 CDT 2009


I like that idea.  These researchers (all PhD types) think they know a
lot about Access...
I've seen their work...scary.

Jim


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Elizabeth.J.Doering at wellsfargo.com
Sent: Thursday, March 19, 2009 9:27 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Dialog Box for Creating .txt tables


 
Where I used to work, we provided a separate .mdb called a Sandbox.
When opened, the Sandbox pulled in a full copy of all the relevant
tables in the BE, and any from the FE, too.  Tables that included our
security settings were excluded!  Users could "play in the sandbox" all
they wanted, without any danger to the live data.  Made them happy and
kept them out of mischief!

HTH,

Liz 

 

This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hewson, Jim 
Sent: Thursday, March 19, 2009 9:13 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Dialog Box for Creating .txt tables

William, your statement below has me intrigued.  
I am working on a proposal for group of researchers that want to be able
to query the data from a questionnaire that students fill out.
You stated below "you have to provide a custom query engine for the
users."
How do you do that?
Thanks,

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William
Hindman
Sent: Thursday, March 19, 2009 2:12 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Dialog Box for Creating .txt tables

...an mde on a full access install only protects your code, not your
data ...a power user wannabe can use a full install to run queries
against the be data that can do immense and sometimes uncorrectable
damage simply because they only "thimk" they know what they are doing
...I've walked away from

jobs over that issue ...I grant that's a luxury others may not have.

...on the other side, that means you have to provide a custom query
engine for the users to have limited access to find the data they need
without my helping hand ...find the data, not modify it in any way that
I don't control.

William

--------------------------------------------------
From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
Sent: Thursday, March 19, 2009 2:06 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Dialog Box for Creating .txt tables

> That's why I keep the MDB tucked away and only let the lusers see the
mde
> :-)
>
> --
> Stuart
>
> On 19 Mar 2009 at 1:54, William Hindman wrote:
>
>> ...we work in different worlds ...I can't imagine an environment
where
>> anyone but me can get to the code ...I'd be serving hard time for
mass
>> maiming, I would.
>>
>> William
>>
>> --------------------------------------------------
>> From: "Max Wanadoo" <max.wanadoo at gmail.com>
>> Sent: Wednesday, March 18, 2009 12:58 PM
>> To: "Access Developers discussion and problem solving"
>> <accessd at databaseadvisors.com>
>> Subject: Re: [AccessD] Dialog Box for Creating .txt tables
>>
>> > I don't use the RT William, just a mdb or mde.
>> > Worth remembering though
>> > Thanks
>> > Max
>> >
>> >
>> > On 3/18/09, William Hindman <wdhindman at dejpolsystems.com> wrote:
>> >>
>> >> Max
>> >>
>> >> ...afaik the FSO doesn't work in a runtime environment ...if
you've 
>> >> got
>> >> it
>> >> working in an A2k3 runtime I'd love to hear how.
>> >>
>> >> William
>> >>
>> >> --------------------------------------------------
>> >> From: "Max Wanadoo" <max.wanadoo at gmail.com>
>> >> Sent: Tuesday, March 17, 2009 8:19 PM
>> >> To: "Access Developers discussion and problem solving"
>> >> <accessd at databaseadvisors.com>
>> >> Subject: Re: [AccessD] Dialog Box for Creating .txt tables
>> >>
>> >>
>> >> > You can also use the FileSystem objects to do this. Just set a 
>> >> > Reference to, oh dear,what was it now...oh yes, I think it was 
>> >> > MS Office 200x.
>> >> >
>> >> > Works better then this (oldish) example.
>> >> >
>> >> > Max
>> >> > ps. Getting late now and it is Paddy's day so the ref may be
worng!
>> >> >
>> >> > On Tue, Mar 17, 2009 at 10:02 PM, Rocky Smolin at Beach Access 
>> >> > Software < rockysmolin at bchacc.com> wrote:
>> >> >
>> >> >> I was just doing this Bud.  I use the code from the Access 
>> >> >> Developer's Handbook - just what you want:
>> >> >>
>> >> >>        lngFlags = adhOFN_HIDEREADONLY Or _
>> >> >>         adhOFN_HIDEREADONLY Or adhOFN_NOCHANGEDIR
>> >> >>
>> >> >>        varFileName = adhCommonFileOpenSave( _
>> >> >>            OpenFile:=False, _
>> >> >>            Filter:=strFilter, _
>> >> >>            flags:=lngFlags, _
>> >> >>            DialogTitle:="Enter File Name and Location for Mail
List
>> >> >> File
>> >> >> Export")
>> >> >>
>> >> >>            varFileName = adhTrimNull(varFileName)
>> >> >>
>> >> >>    intReply = MsgBox("Ready To Export Mailing List " & 
>> >> >> txtMailingList _
>> >> >>        & " to " & varFileName & ". OK to continue", vbYesNo)
>> >> >>    If intReply <> vbYes Then
>> >> >>        MsgBox "Export Aborted.", vbExclamation
>> >> >>        Exit Sub
>> >> >>    Else
>> >> >>        'DoCmd.TransferSpreadsheet acExportDelim, , 
>> >> >> "qryExportMailingList", varFileName, True
>> >> >>        DoCmd.TransferSpreadsheet acExportDelim, 
>> >> >> acSpreadsheetTypeExcel9, "qryExportMailingList", varFileName, 
>> >> >> True
>> >> >>
>> >> >>        MsgBox "Mail List Exported.", vbExclamation
>> >> >>    End If
>> >> >>
>> >> >>
>> >> >> Of course, my transfer is failing but the file name ends up in
the 
>> >> >> var
>> >> >> just
>> >> >> fine.
>> >> >>
>> >> >> Rocky Smolin
>> >> >> Beach Access Software
>> >> >> 858-259-4334
>> >> >> www.e-z-mrp.com
>> >> >> www.bchacc.com
>> >> >>
>> >> >>
>> >> >>
>> >> >> -----Original Message-----
>> >> >> From: accessd-bounces at databaseadvisors.com
>> >> >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bud
Goss
>> >> >> Sent: Tuesday, March 17, 2009 2:45 PM
>> >> >> To: Access Group
>> >> >> Subject: [AccessD] Dialog Box for Creating .txt tables
>> >> >>
>> >> >> I have an Access application that creates a text (.txt) table
using
>> >> >> DoCmd.TransferText.
>> >> >>
>> >> >> In this application, I would like to display a windows dialog
box
>> >> showing
>> >> >> "Save in;" and "File name:" that would allow the user to
navigate 
>> >> >> to
>> >> >> the
>> >> >> directory where the table would be located and designate file
name 
>> >> >> to
>> >> >> be
>> >> >> used.
>> >> >> (Similar to the dialog box that you see when you do a file save
as 
>> >> >> in
>> >> >> Microsoft word etc.)
>> >> >>
>> >> >> Is it possible to do this in Access?
>> >> >>
>> >> >> If so, would some one tell me where I can find information and 
>> >> >> examples.
>> >> >> --
>> >> >> 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
>> >> >>
>> >>
>> >> > --
>> >>
>> >> > 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
>> >>
>> > --
>> > 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
>>
>
>
>
> --
> 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
########################################################################
########
If you have received this message in error, please contact the sender
immediately and be aware that the use, copying, or dissemination of 
this information is prohibited. This email transmission contains 
information from NCI Information Systems, Inc. that may be considered 
privileged or confidential and is intended solely for the named 
recipient.
########################################################################
########

-- 
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
################################################################################
If you have received this message in error, please contact the sender
immediately and be aware that the use, copying, or dissemination of 
this information is prohibited. This email transmission contains 
information from NCI Information Systems, Inc. that may be considered 
privileged or confidential and is intended solely for the named 
recipient.
################################################################################




More information about the AccessD mailing list