Hi Chip:
A similar situation happened to me a few days ago, I forgot which script I
was trying to repackage. To get around the problem, I just created a new
package.
That might not explain what is going on, but it seemed to be the easiest and
fastest way to accomplish what I wanted to do.
Kevin Huber
----- Original Message -----
From: "Allison and Chip Orange" <[email protected]>
To: <[email protected]>
Sent: Monday, June 29, 2009 6:39 PM
Subject: are .wepm files from earlier versions compatible?
Hi all,
I'm trying to modify a .wepm file from WE 7.01, and after I choose to
modify
an existing package, and select it from the list, the package editor
simply
closes with no explanation and I'm back in WE.
anyone have any ideas as to what's going on?
thanks.
Chip
__________ Information from ESET Smart Security, version of virus
signature database 4205 (20090701) __________
The message was checked by ESET Smart Security.
http://www.eset.com
