S
skeebuni
I developed an Issue Tracking system using Access 2003 while my operating
system was Windows 2000. My hard drive crashed and I was upgraded to Windows
XP. I have Office 2003/Access 2003 reinstalled on my new machine.
I also have Visual Studio
All other users of the DAP's can still access/update the database fine.
I am the only one having this problem.
My pre-existing data access pages come up as read-only for me.
I thought this might be some sort of licensing issue....but if I create a
new DAP I can add/update records fine (We have an enterprise license so I
thought I would be okay). I have looked at the pre-existing and new source
files for the DAPS and they both use the same version of the OWC's
(10.0.0.6712). I see a slight difference in the Connection strings (one has
Persist Security Info false and one true, and one has password = "" the other
no password parameter at all)
I am at a loss as to what I can look at next. If anyone could help point me
in the correct direction it would be greatly appreciated!!
system was Windows 2000. My hard drive crashed and I was upgraded to Windows
XP. I have Office 2003/Access 2003 reinstalled on my new machine.
I also have Visual Studio
All other users of the DAP's can still access/update the database fine.
I am the only one having this problem.
My pre-existing data access pages come up as read-only for me.
I thought this might be some sort of licensing issue....but if I create a
new DAP I can add/update records fine (We have an enterprise license so I
thought I would be okay). I have looked at the pre-existing and new source
files for the DAPS and they both use the same version of the OWC's
(10.0.0.6712). I see a slight difference in the Connection strings (one has
Persist Security Info false and one true, and one has password = "" the other
no password parameter at all)
I am at a loss as to what I can look at next. If anyone could help point me
in the correct direction it would be greatly appreciated!!