Search results

Make sure to take a photo of the shrine -- I'll keep that in my office. :)

Shouldn't you skip the updating of the table if you issue an error to the user? I'm thinking you need to wrap an If statement around your recordset code: Private Sub cmdAddEntry_Click() On Error GoTo Err_cmdAddEntry_Click Dim strSQLClaims As String Dim strSQLRCN As String dim blnError as...

I'll take that. :D

Try this: =Format([Begin Date],"mmm d"", ""yyyy") & " and " & Format([End Date],"mmm d"", ""yyyy")

If you're using the recordset example you can do it this way: 1. Make your claims recordset and add the new record like my example shows. 2. Make a second recordset for the RCN table and add your new record to that one. When you get to adding the intClaimID field, you can do something like...

Yeah, you're controlsource should be something like: =Format([BeginDate],"your format here")...

Is is because you need the intClaimID field to be filled into tblRCN?

No problem -- I've had that problem numerous times. I've actually abandoned using the parameters in the query and instead referencing a textbox on a form where the user enters a date. They work the same way.

They have to be spelled exactly the same. It looks like you've got [Begin Date] in the query and [BeginDate] on the report. You either need to put the space on the report or take out the space in the query.

So then you just need two textboxes on your report. One that contains [Begin Date] and another with [End Date]. I can't remember if you need an = before the bracket...

Yeah, rather than just typing in "SELECT * FROM [table]" as the recordset source, you should be able to use a SELECT statement with joins. Just make sure that the primary key from both tables are included in the SELECT statement, and that should make your recordset updatable. Is there a reason...

In your query, have you put in parameters like [From:] and [To:]? If so, you should be able to put those into textboxes on the report by typing in the exact same names.

Sel, There's two ways you can go about doing this -- one with a recordset and one without. Using recordsets, you could do it this way: Private Sub cmdAddEntry_Click() On Error GoTo Err_cmdAddEntry_Click Dim strSQL As String Dim cnCurrent As ADODB.Connection Set cnCurrent =...

I'm actually going to be using ASP.net 2.0. I had taken a VB.net course back in the fall and my instructor was encouraging me to give ASP.net a try and see if it'll work for what I want to do. And that's where I am. :)

Thanks a bunch! I've got some reading to do! I've done Access/VB for a while now, but ASP seems a little foreign to me. Hopefully this does the trick. :)

Hi, I've been creating database apps for a while now with SQL Server back-ends and Access 2000 front-ends. We've just recently purchased Visual Studio 2005 and I'm looking to try using an ASP front-end instead of Access. The idea was to have the ASP app on our company intranet and thereby...

Based on your previous response, you said that there are laws to punish criminals and that by not punishing them we are creating anarchy. My response is that they should be punished, but not by killing them.

Okay, lets say for the sake of argument that the correct translation is "Thou shalt not murder." The argument is that murder is pre-meditated. Based on the Mirriam-Webster Dictionary, premeditated is defined as: "characterized by fully conscious willful intent and a measure of forethought and...

I'm not saying we shouldn't punish criminals. I'm saying that the punishment does not have to be the death penalty.

Isn't there an Oliver Stone film about September 11 coming soon? Edit: Here's a link: http://www.imdb.com/title/tt0469641/