Quote - poser content or at least alot of it can be used in daz.  poser dynamics cannot be and i don't think poser procedural textures/materials can be either

Poser shaders, including the procedural materials can be re-created in the new Studio shader system (Advanced version). The new shader mixer is a big improvement compared to the shader included in previous versions of Studio.

You should really take a look at the morph injection docs on the DAZ 3D site, there's a lot of details that can help you.
The skinny: you can inject a morph via a PZ2 if the original CR2 has a morph channel available or if you want to overwrite an existing morph channel. 
Once you have your morph you can use this script http://forum.daz3d.com/viewtopic.php?p=649451#649451
to create the INJ/REM files.
If you have made your figure yourself and you want to include the morph to it simply save the file as a CR2 and it will work for both Poser and Studio.

If you develop under Studio you should use the Morphg Loader/Morph Loader Pro and then the Figure Setup Tool Bundle with the CR2 exporter. Those are great tools that make the job of creating Poser figures a lot simpler than what is in Poser.

Hope this helps

 Glad it worked for you Holly. Have fun with Studio.

Are you sure that you're looking t the scene through the same camera? Is it possible that you switched camera? You could create a new camera in order to avoid using the  default one or the Perspective view, the latter not being a real camera, and once you have the scene framed right, select the camera in the scene pane so that it becomes the active object and then  you can press 'Shift-L" to lock it. This will prevent any parameter to be changed until you unlock the object.

 You are not giving us many information to judge what is the problem. If the figure is a morph for V4, then it should work in Studio. Pose files are generally used to inject morph into V4, that's the normal way since V4 has numerous injection channels. Before you buy the Morph++, which are a good deal, check if  NaikaV4 requires them. The author should provide the information including what exactly is not working in Studio. Generally when authors warn about Studio incompatibilities it refers to shaders and those can be recreated in Studio with a bit of experimentation.

Inocentral, a Poser figure is composed by several files. There is the geometry file which describes the set of vertices and faces that create the base geometry. There are CR2 and PZ2 file which define the joints, bones, materials and poses. All these files are collected inside a pretty well defined directory structure. 
From a "root" directory you will find a sibdir called "Runtime". Underneath you will find directories with names like "Geometries", "Library" etc. 
Those directories define what is referred to as the Poser Runtime. DAZ Studio reads that structure as well. When you install a figure you add files to that repository/library/runtime (all valid names).
Take a look at it with your file manager of choice and read the documentation. It's overwhelming at first but after a bit of frustration it generally starts to make sense :)

Quote - I'm still not clear on creating an external directory for both Studio Advanced and Poser Pro.  I go into Poser Pro and select add an external directory.  Then add Daz Studio directories into that?  Then there is the question of auto content installers too...

You have to create an new directory, you do that via your file manager. If you're on Mac OS use the finder, I suggest to create a folder in your home folder. If you're under Windows select the equivalent of your home dir and create a subdir in it. Whe you install new content don't select the automatic installation, click on the button to select the dir and then point to the directory that you have created.

 No need for an external drive, just keep the files in a separate folder, away from the application's folder. Poser has the tendency to use a Runtime dir inside the applications dir. Don't do that. 
I have series of dirs under ~/DSContent  that is shared both by DS and Poser. 

For example:
~/DSContent/Morphs
~/DSContent/Clothing
~/DSContent/Textures

and so on. 
In DS use the configure option and add each directory to the the Poser directory list. Just point to the same dirs in Poser as well. Keeping the content separate from the application makes it easy to update the application without losing your content. You don't need a separate drive, just a separate dir.

 Hi Esther.
This problem is usually related to the way some CR2 are built. The correct path to refer to an OBJ is something like:

:Runtime:Geometries:product_dir:product_file.obj

I noticed that several products made for Poser use this path instead:

Runtime:Geometries:product_dir:product_file.obj

Note the missing ":" at the beginning. If you open the CR2 file and correct the path for the figureResFile statement, it should fix this problem. 

 I made a short video tutorial about OBJ export an loading the model in Blender, maybe it will help you:
http://www.youtube.com/watch?v=u7-7JJ5IoZg 

Well, if you have a Poser file then it works in Studio, you don't have to do anything. Or am I missing something here?
 

What format is the prop? Are you importing an .OBJ or you have the Poser file?
 

 The content database might be corrupted. Take note of  your configuration, the Runtime directories that you have added. Clear the database, close Studio, restart it and then add the directories again and try the scan again.

 I think it came out about 7-10 days ago. It is free but there is the Advanced version with additional features. I think they are having a limited time sale.

 Look in the documentation, very likely the materials have been designed for Poser and didn't translate into Studio completely. If you're using Studio 2.x I would also suggest to upgrade to 3.x as it has more sophisticated shaders. 
If you can let us know exactly what changes you have applied to the shaders. "Pokig around" with shaders is a sure recipe for losing track of time :). I would suggest to try to change one parameter at the time, check the result, if it doesn't work Undo and continue. Changing multiple shader parameters at the time can lead to a lot of frustration and no results. I know by experience :)