Packaging Wizard Help! High Priority

[Ima Lostsoul]

I am having issues with the packaging wizard in Access Developers
Edition XP. Here is the deal.
The program uses a system file. There are three total databases (front
end, common data, and user data). The front end is in a parent
directory with each of the otehr two in their own directory underneath
that. I am generating a run time distribution...

When I use the version of the program that does not use a custom system
file all goes well.

When I use the live version, I get an error when I point to the front
end (main file) that it is corrupt or otehrwise unusable. I cannot seem
to build the runtime package with the live version using the custom
system file.

So I decide to create it using the unprotected and then try to replace
the main MDB file with the live one by using the 'command to run after
installation' routine in the wizard. I cannot get this to work at all.
No matter what I put in the command to run afterwardsm, nothing happens.

Can anyone please help me here? I am at a major roll out of a program
and I am stuck like a sheep next to a lonely farmboy in West Virginia!
DB

[r0adh0g]

I've had some similar deployment problems as well.
I ended up writing a ms dos batch file to create the
folders that I wanted and to copy them where I wanted
as well as desktop and start menu shortcuts. Then installing
A2k2 runtime on it own. It going around your asshole to get
to your elbow, but it works.
My $0.02

rh
"Ima Lostsoul" <[e-mail]> wrote in message
news:MP************************@netnews.comcast.ne t...

I am having issues with the packaging wizard in Access Developers
Edition XP. Here is the deal.
The program uses a system file. There are three total databases (front
end, common data, and user data). The front end is in a parent
directory with each of the otehr two in their own directory underneath
that. I am generating a run time distribution...

When I use the version of the program that does not use a custom system
file all goes well.

When I use the live version, I get an error when I point to the front
end (main file) that it is corrupt or otehrwise unusable. I cannot seem
to build the runtime package with the live version using the custom
system file.

So I decide to create it using the unprotected and then try to replace
the main MDB file with the live one by using the 'command to run after
installation' routine in the wizard. I cannot get this to work at all.
No matter what I put in the command to run afterwardsm, nothing happens.

Can anyone please help me here? I am at a major roll out of a program
and I am stuck like a sheep next to a lonely farmboy in West Virginia!
DB

[MacDermott]

What is the System file your database uses?
Do you mean an mdw file for security?

- Turtle

"Ima Lostsoul" <[e-mail]> wrote in message
news:MP************************@netnews.comcast.ne t...

I am having issues with the packaging wizard in Access Developers
Edition XP. Here is the deal.
The program uses a system file. There are three total databases (front
end, common data, and user data). The front end is in a parent
directory with each of the otehr two in their own directory underneath
that. I am generating a run time distribution...

When I use the version of the program that does not use a custom system
file all goes well.

When I use the live version, I get an error when I point to the front
end (main file) that it is corrupt or otehrwise unusable. I cannot seem
to build the runtime package with the live version using the custom
system file.

So I decide to create it using the unprotected and then try to replace
the main MDB file with the live one by using the 'command to run after
installation' routine in the wizard. I cannot get this to work at all.
No matter what I put in the command to run afterwardsm, nothing happens.

Can anyone please help me here? I am at a major roll out of a program
and I am stuck like a sheep next to a lonely farmboy in West Virginia!
DB