Making a new ms access project

I'm having trouble making a new ms access project.
MSDE is running.
I run the wizard and it asks for a user name and password for the new
database. I put in sa and leave the password blank. Then I get an error
message.
What should I do?
Thanks.
Also, do the tables actually reside on in the sql file and the project
links to them? Where is there a tutorial on this?
Thanks again.
I found out the the Symantec Personal Firewall was blocking this.
Which program do I need to have it allow to have access? Ms Access?
Thanks.
"SAC" <someone@.microsoft.com> wrote in message
news:%23F2BGbG6EHA.3616@.TK2MSFTNGP11.phx.gbl...
> I'm having trouble making a new ms access project.
> MSDE is running.
> I run the wizard and it asks for a user name and password for the new
> database. I put in sa and leave the password blank. Then I get an error
> message.
> What should I do?
> Thanks.
> Also, do the tables actually reside on in the sql file and the project
> links to them? Where is there a tutorial on this?
> Thanks again.
>

Make SQL Agent use drive mapping?

Good day,
I'm migrating our current SQL 2k box (running on win 2000) to a new Windows 2003 server. I'm having trouble getting the SQL agent to use the servers drive mapping when running jobs. The odbc driver that I'm using does not support UNC paths. I know, dri
ve mapping are not cool becuase we have to keep the server logged in but it's the only way and it does work on our old box. The weird thing is that I can't get this working on the new server. On the old box the SQL Agent is set to run as the same accoun
t as the logged in user and it can access the drive mappings fine, it's been running this way for quite some time. However, on my new box this does not work...is this a windows 2003 server thing? I'm runing SQL 2k SP3 on both boxes. Also, the new box i
n not in a domain so the account I'm trying to use is a local admin acount.
Any ideas?
Drive mappings are not guaranteed to work when being accessed from a
service. There is no way to force them to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I figured it out. I simply added a step in each scheduled job to create and then delete the drive mapping.
For example, I just use the "net use f: \\server\volume" to create the drive ampping an then excute the rest of my job steps and then use another step with this command "net use f: /delete" to delete it. Becuase the SQL Agent service is excuting the comm
and the drive mapping is in it's session and it works every time. It's nice becuase the drive mapping isn't even seen by the desktop and works when the server in not logged in. I remove the drive mapping at the end of each job becuase the drive mapping
remains in tack as long as the SQL agent service stays running and therefore if another job runs and tries to re-create the drive mapping the job will fail.

Make SQL Agent use drive mapping?

Good day,
I'm migrating our current SQL 2k box (running on win 2000) to a new Windows
2003 server. I'm having trouble getting the SQL agent to use the servers dr
ive mapping when running jobs. The odbc driver that I'm using does not supp
ort UNC paths. I know, dri
ve mapping are not cool becuase we have to keep the server logged in but it'
s the only way and it does work on our old box. The weird thing is that I c
an't get this working on the new server. On the old box the SQL Agent is se
t to run as the same accoun
t as the logged in user and it can access the drive mappings fine, it's been
running this way for quite some time. However, on my new box this does not
work...is this a windows 2003 server thing? I'm runing SQL 2k SP3 on both
boxes. Also, the new box i
n not in a domain so the account I'm trying to use is a local admin acount.
Any ideas?Drive mappings are not guaranteed to work when being accessed from a
service. There is no way to force them to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I figured it out. I simply added a step in each scheduled job to create and
then delete the drive mapping.
For example, I just use the "net use f: \\server\volume" to create the drive
ampping an then excute the rest of my job steps and then use another step w
ith this command "net use f: /delete" to delete it. Becuase the SQL Agent s
ervice is excuting the comm
and the drive mapping is in it's session and it works every time. It's nice
becuase the drive mapping isn't even seen by the desktop and works when the
server in not logged in. I remove the drive mapping at the end of each job
becuase the drive mapping
remains in tack as long as the SQL agent service stays running and therefore
if another job runs and tries to re-create the drive mapping the job will f
ail.

Maintenance Plan Wizard is Crashing

Hi,

I am having trouble with the Maintenance Plan Wizard in SQL Server 2005 Management Studio.

I have run the Maintenance Plan Wizard many times since I installed SQL Server 2005. However it looks like there is a problem with assembly 'Microsoft.SqlServer.Smo. I am getting this error:

- Creating maintenance plan "DNNSRC Backup" (Error)
Messages
* Create maintenance plan failed.

ADDITIONAL INFORMATION:
Could not load type 'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'. (Microsoft.SqlServer.MaintenancePlanTasks)

Note I was going to upgrade with service pack 2 but I am reluctant to do that until I fix this problem. I am not sure SP2 would have any effect.

Any help or suggestions would be very much appreciated.

Thanks.
G. M.

make sure that your system is upgraded to SP2 and also you have installed SSIS.

Refer these links for more info

http://support.microsoft.com/default.aspx/kb/933508

http://blogs.msdn.com/sqlrem/

Madhu

|||

Check the following thread...sp2 resolve the same issue...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1404000&SiteID=1

|||Thanks, Your suggestions helped. I installed SP2 and that corrected the problem.