Thanks....
This happens when 2 XP users with write privs access the database... I also tried giving write privs on the folder to all authenticated users.. (no luck)...
I have an Access database on a share drive that is set to multi-user, no locks.... I'm using folder security to control access to it. All authenticated users have read access and about 4 folks have read/write to this folder... The database itself is Access 2003 in a 2000 format. Until...
I have a combination of Access 2000 and Access 2003 users. My application was developed in a 2003 version of Access. The production version of this application is on share drive. I have a form that uses a query for a the record source. That query is set "record lock = no lock".... My problem...
Thanks, that is kind of where I was heading. I was thinking that I could create my own table of users and groups and then apply privs accordingly.... I can grab the username from the network so I don't really need to bother the use with a login screen.
But I don't want to go down that path if...
I'm not trying to be flip, but could getting security to work in Access be any more difficult? Ok, I've got that off of my chest....
I'm running Access 2003. And I don't need a boatload of security. My application will be accessed from a share drive in a fairly secure environment. The drive...
I would like to use Excel as a report writer to use with and aspx page. What I'd like to do it create an aspx page that accepts various parameters. Then it passes these parameters to an excel application on the web server that runs whatever it needs to run in order to get the right format for...
Thanks
Frankly, the Microsoft documentation on many things leave much to be desired (understatement). Advice from folks like yourself is what makes working with this stuff tolerable.
Thanks again
OracleVictim
Boy this is just what I'm trying to do. All I want is the name of the user accessing the page. I've embedded
"Request.ServerVariables("LOGON_USER")" in my page load event and get nothing. It looks like I'm probably set to accept an annonymous login and that may be my problem. However, I don't...
Thanks. I used single quotes in the source SQL statement and it works just fine..... IIf([completion_code]='1','Complete','Cancelled'). If I use this expression on the report (e.g. expression builder), I get a #Error.
But this works for Now. I'm assuming there must be something about...
Thanks
Actually this is a query on an original passthrough. I've tried changing my double quotes to single quotes and am still not having luck. How would you fix the following to make it go?
=IIf([completion_code]='1',"Complete","Cancelled")
Thanks again
Oraclevictim
(if you've seen this post before, sorry....I accidentally posted this as a response)
I'm trying to get a simple expression in the Access report writer to work properly. Essentially if I use:
=IIf([COMPLETION_CODE]="1","Conducted","Cancelled") or...
I'm trying get a simple expression in the Access report writer to work properly. Essentially if I use:
=IIf([COMPLETION_CODE]="1","Conducted","Cancelled")
I get an error. Yet, if I run the following...
Has anyone experienced this? I have Crystal .rpt files written using Crystal 8.5. These reports are presently acccessed with a VB client using a Crystal Viewer object.
I installed .Net on my developer workstation. It comes with Crystal 9. I modified a .rpt file using Crystal 9 and now it...
Thanks again. I found the MDAC 2.5 and installed it on my NT machine, but no luck.
I'm pretty sure I'm deep in dll hell. I've rewritten the application to use a simple text file for input and that seems to work fine. But it seems like this should work with Excel.........
I'm running VB6 on Windows NT.
I have a little application that uses a data object to bind a datagrid to an Excel spreadsheet. All was well until I upgraded my Office97 to Office 2000. Now when I launch this application and try and connect to my Excel datasource I get the following error...
Thanks much.
This sounds very familiar. We are running 8.1.7. We installed the 8.1.7.4 patch on a test machine and this seemed to introduce problems with some of our views.
So, what I'm hearing from you is that you recall 8.1.7 having a bug that prevented this fix from working properly...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.