Recent content by SMerrill

And my thought was that once you re-created the table, the old corrupt table would be gone and the new one should not fail from then on. Take care, --Shaun Merrill Seattle, WA

Permissions don't get "wiped out". They are simply cumulative. It's rather like a key and a lock. The keys are stored in the MDW and the locks are formed within each MDB explicitly. The only "adopted" permissions are database owner permissions. You will have to get the...

Simply re-create the table and populate it with data from the old table. Make sure to put in the keys and relationships. Take care, --Shaun Merrill Seattle, WA

Please look up "Exclusive Access" in the help documentation. Take care, --Shaun Merrill Seattle, WA

Did Division log into the MDW when they were developing the MDE file? Division must have a copy of the MDB which they converted and published to you as an MDE file. Furthermore, they must be able to get into their MDB copy as administrators. So ask them to ensure that your MDE works with...

Be wary of Access 2000. Go directly to Access XP. Take care, --Shaun Merrill Seattle, WA

The front end and the back end should belong to the same System.MDW (workgroup) thus enjoying the same security model. Your connection occurs because the default username is "Admin" and the default password is blank. If you put the front and the back in the same workgroup, the user...

I have successfully made a recordset object full of data from a parameterized SQL Server stored procedure. Now I would like to quickly zap the resulting recordset object into an Access Table so I can use it as the source for an append query. I would like to avoid looping through the recordset...

Nice thought. I explicitly defined those constants myself with the CONST command. But just on a whim, I tried the literal string dates exactly as you had typed, and IT WORKED! What I had been hiding from the forum was the fact that I was trying to do this in very generic ASP code, passing the...

So the program you pointed me to is set up to choose only from the default values. I cannot ad-hoc enter a date-range parameter using the form provided. I wish when Crystal Decisions made a VB example, they would make the user interface as close as possible to the one that comes up when you...

Specifically, I am using PDSOLEDB.DLL connecting to SQL 7. Take care, --Shaun Merrill Seattle, WA

Thanks for trying to help me solve this. There must be something wrong with the date parameter settings still, since I can run them directly from the RPT design view (CR version 8.5.) I am tempted to send you the CR file, but you couldn't tie in to my ADO database. Using the very helpful VB...

Thanks. I found and removed the .EnableRangeLimit=True line, which got rid of the error. I am now only using the ClearCurrentRangeAndValue and the AddCurrentRange methods. The main difference is that I am using VBScript and you seem to be using an early-binding version, perhaps Visual Basic...

When I put in your code, an error occured just after the call to oRpt.ReadRecords: "The parameter value is not in the range limit." Take care, --Shaun Merrill Seattle, WA

Yeah, it was a typo in the snippet that I made when I was trying to pare it down to size. I have also tried to add this code both before and after setting the Maximum and Minimum values, and it still doesn't do what I want. If I put it in Before setting them, I get all records. If I put it in...