[AccessD] Changing Column Width and Order in mde or accde
Gustav Brock
gustav at cactus.dk
Wed Nov 1 11:56:41 CDT 2017
Hi Bill
That could be done. But why an Excel file? You could just as well link a small Access file.
/gustav
-----Oprindelig meddelelse-----
Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af Bill Benson
Sendt: 1. november 2017 17:01
Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Emne: Re: [AccessD] Changing Column Width and Order in mde or accde
Can one accde import data from another (prior version ) accde? I know I did that all the time with accdb, but haven't tried with an accde to accde handoff.
Or by using a linked Excel table that is created in the same directory as the accde resides on first load?
I don't know a lot about accdes, whether they can have tables be linked on demand, but surely I could very easily write a routine in VBA that reads from an excel or csv file to import such retained data, and similarly export as well, making the solution transportable, and the app path very easy to determine.
Think creatively, I don't think this is hard. Or maybe I am all wet....
On Nov 1, 2017 9:41 AM, "Gustav Brock" <gustav at cactus.dk> wrote:
> Sure Bill, but how do you preserve the settings, if/when the frontend
> is replaced by a new version?
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af
> Bill Benson
> Sendt: 1. november 2017 14:34
> Til: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Emne: Re: [AccessD] Changing Column Width and Order in mde or accde
>
> My solution already demonstrated that no external items are required.
> Maintaining a table inside the MDE/ACCDE works just fine.
>
> On Wed, Nov 1, 2017 at 9:12 AM, Rocky Smolin <rockysmolin at bchacc.com>
> wrote:
>
> > Gustav:
> >
> > Well that's true - they would have to re-establish their preferences.
> > So putting those setting in an external mdb/accdb or a text file
> > which would reside in the user's front end folder would solve that, yes?
> >
> > R
> >
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On
> > Behalf Of Gustav Brock
> > Sent: Wednesday, November 01, 2017 1:03 AM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Changing Column Width and Order in mde or
> > accde
> >
> > Hi Rocky
> >
> > Or maybe not, as all settings will be lost when you update the frontend.
> > We used a separate backend for storing user settings.
> >
> > /gustav
> >
> > -----Oprindelig meddelelse-----
> > Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne
> > af Rocky Smolin
> > Sendt: 31. oktober 2017 22:19
> > Til: 'Access Developers discussion and problem solving' <
> > accessd at databaseadvisors.com>
> > Emne: Re: [AccessD] Changing Column Width and Order in mde or accde
> >
> > As I think about it, since it would be an advantage to let each use
> > save their own field order and widths, saving the properties in a
> > front end table might be an advantage.
> >
> > R
> >
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On
> > Behalf Of Jim Lawrence
> > Sent: Tuesday, October 31, 2017 1:40 PM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Changing Column Width and Order in mde or
> > accde
> >
> > An excellent method to save your last position.
> >
> > I did a similar process many years ago with VB. Had a module that
> > would open a registry set and then loop around pushing all global
> > variables and position variable into the stack. When the application
> > opened again, even after a system update, each user would have the
> > environment they exited with...if they so chose. Unfortunately, even
> > with the best efforts it was never a hundred percent.
> >
> > We do now have some excellent sync tools which could make much of
> > that type of work redundant.
> >
> > Jim
> >
> > ----- Original Message -----
> > From: "Gustav Brock" <gustav at cactus.dk>
> > To: "Access Developers discussion and problem solving" <
> > accessd at databaseadvisors.com>
> > Sent: Tuesday, October 31, 2017 12:33:54 AM
> > Subject: Re: [AccessD] Changing Column Width and Order in mde or
> > accde
> >
> > Hi Stuart
> >
> > Oh no. "All you need" is to read and save the properties of the
> > columns to a set (a tree) of tables before closing the form, then
> > read from the tables and restore the settings when opening the form.
> >
> > I once wrote a full system for a client who wanted this feature. It
> > went a bit like this:
> >
> > ID UserSettingFormSubformID Name ColumnOrder ColumnWidth
> > ColumnHidden
> > 1 1 ID 1 -1 Sand
> > 2 1 Dimension 2 1875 Sand
> > 3 1 DimensionElementOrder 4 -1 Falsk
> > 4 1 DimensionElement 3 1995 Falsk
> > 5 1 DimensionElementProportion 5 2850 Falsk
> >
> > Those basic settings are not difficult. The challenge is the get
> > hold on frozen columns. Sort order for each column was also added.
> >
> > I considered writing an article about this but gave up, as the setup
> > was heavily intermixed with application settings for Format and
> > Conditional Formatting, as well as default settings which - and this
> > is important - the user could choose to revert to in case he/she got
> > the layout garbled beyond easy restoring at the user level.
> >
> > Add to this maintenance of the settings. It was a large application
> > and just about all forms had subforms in datasheetview. We made a
> > function to rebuild all the current settings as default settings;
> > this function was called when the user belonged to the developer
> > group of
> users.
> >
> > /gustav
> >
> >
> > -----Oprindelig meddelelse-----
> > Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne
> > af Stuart McLachlan
> > Sendt: 30. oktober 2017 21:58
> > Til: Access Developers discussion and problem solving <
> > accessd at databaseadvisors.com>
> > Emne: Re: [AccessD] Changing Column Width and Order in mde or accde
> >
> > Just found this - turns out you need to manipulate the Registry!!!
More information about the AccessD
mailing list