Porting 2003 ==> 2007: How Did You Backfill For /INI?

[(PeteCresswell)]

I'm finally forced to migrate my first production app from 2003 to 2007.

All my apps use the /INI parameter on the command line that opens
MSACCESS.EXE. Basically, I pass the path to the file containing my
.INI file. e.g. "C:\Program Files\Microsoft
Office\OFFICE11\MSACCESS.EXE" /INI D:\SFIM\DEVELOP.INI

2007, of course, dropped support for that parm.

The Question:

How did you code around this?

My kneejerk reaction is to parse the .CMD variable.
--
Pete Cresswell

[Douglas J Steele]

You could write a function that deals with your .INI file and call it on
startup.

"(PeteCresswell)" wrote in message
news:q6uno8l1uvsjqqj0q...@4ax.com...

[(PeteCresswell)]

Per Douglas J Steele:

>You could write a function that deals with your .INI file and call it on
>startup.

What I wound up doing is:

- Passing "/CMD "inifileURL+workdirectory" on the MS Access command
line.

- First thing in AutoExec, parsing Command() into it's two components.

- From the array returned by the parse, extracting the two components
into global variables gIniFilePath and gTempDirectory.

- Replacing all occurrences of Syscmd(SyscmdIniFile) with gIniFilePath.

Stumbled a little over the string and the plus sign before I realized
the entire string had tb in quotes and not each component.

But it seems to work reliably.

Now it's on to various weird nesses in 2007.....
--
Pete Cresswell