Complex Samples Problem

[jtjordan]

Hello,

I'm running into the same problem that Tammy Campbell ran in to back in 10/12, but I don't think there was any response:

"I'm trying to perform weighted analysis using the complex samples module, and everything seems to go okay at first: I set up the plan file and it shows up in the location where I save it. However, when I try to call it up to perform analysis, I get an error message saying 'plan file is not found.' This is really odd because I can see that it's right there as specified."

Any help on this would be greatly appreciated!!

[Art Kendall]

When I had this problem, I had made a slight error in the specification.
If you are in windows
navigate to the folder the file is in
put you cursor on the file and
right click it
click "properties"
copy the filespec
Paste the filespec into your syntax.
look for differences like direction of slashes spaces etc.

On 10/8/2013 2:08 PM, jtjordan [via SPSSX Discussion] wrote:

Hello,

I'm running into the same problem that Tammy Campbell ran in to back in 10/12, but I don't think there was any response:

"I'm trying to perform weighted analysis using the complex samples module, and everything seems to go okay at first: I set up the plan file and it shows up in the location where I save it. However, when I try to call it up to perform analysis, I get an error message saying 'plan file is not found.' This is really odd because I can see that it's right there as specified."

Any help on this would be greatly appreciated!!

---

If you reply to this email, your message will be added to the discussion below:

http://spssx-discussion.1045642.n5.nabble.com/Complex-Samples-Problem-tp5722447.html

To start a new topic under SPSSX Discussion, email [hidden email]
To unsubscribe from SPSSX Discussion, click here.
NAML

[jtjordan]

Thanks for the quick response!

Unless I'm overlooking something, everything matches up perfectly - slashes, spaces, even capitalization. Are there any other reasons why this might be happening, or is it possible I'm just missing something?

[Rich Ulrich]

[re: "plan file not found"]
Here's a chance to find out if that old DOS legacy-headache still exists,
that early adaptation to the days when file names could not include a blank --

Try putting quotes around anything with a blank,
  .... /two words/file 1.sav      becomes
  ..../"two words"/"file 1.sav"   .

--
Rich Ulrich

> Date: Tue, 8 Oct 2013 15:17:15 -0700

> From: [hidden email]
> Subject: Re: Complex Samples Problem
> To: [hidden email]
>
> Thanks for the quick response!
>
> Unless I'm overlooking something, everything matches up perfectly - slashes,
> spaces, even capitalization. Are there any other reasons why this might be
> happening, or is it possible I'm just missing something?
>
>
>

[Art Kendall]

Over the years there have occasional problems with the direction of slashes, I cannot recall when it makes a difference which way the slashes go.

I have at times had problems with filespecs that were long and/or included spaces.  I have worked around this by using names with underscores rather than blanks then
by creating a pseudo disk, or [haven't used this one in a decade or so]
by putting things on an external drive, or
just putting a folder near the root like c:\abc  and shortening the whole name.

The shorter filespecs without spaces in names worked around the problem.
However the problem has not been consistent enough that I can describe when it does or does not occur.
On 10/8/2013 6:17 PM, jtjordan [via SPSSX Discussion] wrote:

Thanks for the quick response!

Unless I'm overlooking something, everything matches up perfectly - slashes, spaces, even capitalization. Are there any other reasons why this might be happening, or is it possible I'm just missing something?

---

If you reply to this email, your message will be added to the discussion below:

http://spssx-discussion.1045642.n5.nabble.com/Complex-Samples-Problem-tp5722447p5722450.html

To start a new topic under SPSSX Discussion, email [hidden email]
To unsubscribe from SPSSX Discussion, click here.
NAML