William Hindman
wdhindman at dejpolsystems.com
Mon Mar 23 16:27:25 CDT 2009
...maybe ...just maybe ...you're really not ready for C# quite yet :)
William
--------------------------------------------------
From: "Max Wanadoo" <max.wanadoo at gmail.com>
Sent: Monday, March 23, 2009 11:35 AM
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Dialog Box for Creating .txt tables
> I know, Just after I pressed the send button I thought how stupid my
> reply
> was. Just image a record with a dozen other tables that require to be
> updated etc depending on what the contents of the first one is.
> Definately
> not practicable to do anything at Table level.
>
> Sorry Charlotte - I withdraw my inane comment.
>
> Max
>
>
> On Mon, Mar 23, 2009 at 3:25 PM, Charlotte Foust
> <cfoust at infostatsystems.com
>> wrote:
>
>> Easy work?? You've never tried to untangle hundreds of tables with
>> thousands of records with data updates being exported and imported
>> between installations!
>>
>> Charlotte Foust
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
>> Sent: Thursday, March 19, 2009 8:12 AM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] Dialog Box for Creating .txt tables
>>
>> But if it is chargeable and you can wave the agreement at them, then it
>> is easy work - no?
>> Max
>>
>>
>> On Thu, Mar 19, 2009 at 3:07 PM, Charlotte Foust
>> <cfoust at infostatsystems.com
>> > wrote:
>>
>> > The problem with that approach is that when THEY break THEIR data, YOU
>>
>> > are the one who gets the phone call. The user attitude tends to be
>> > "it's YOUR program" that caused the problem.
>> >
>> > Charlotte Foust
>> >
>> > -----Original Message-----
>> > From: accessd-bounces at databaseadvisors.com
>> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
>> > Sent: Thursday, March 19, 2009 12:28 AM
>> > To: Access Developers discussion and problem solving
>> > Subject: Re: [AccessD] Dialog Box for Creating .txt tables
>> >
>> > William,
>> >
>> > > .an mde on a full access install only protects your code, not your
>> > > data
>> >
>> > It is not YOUR data, it is THEIR data. I would only be interested in
>> > protecting MY code but I would give them security over their data as
>> > part of the package. An MDE protects the application (as you say).
>> >
>> > Max
>> >
>> >
>> > On 3/19/09, William Hindman <wdhindman at dejpolsystems.com> wrote:
>> > >
>> > > ...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
>> > >
>> > --
>> > 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
>