• WSPatricia W

    WSPatricia W

    @wspatricia-w

    Viewing 15 replies - 16 through 30 (of 237 total)
    Author
    Replies
    • in reply to: Connect to SQL Server via VBA (2003 SP 3) #1112707

      Ken — I think your “EXEC SDUpdate @SID = ” is fine, if SDUpdate is the actual name of your procedure. I have the Chr(34) around the procedure name because it is a variable containing the name of the procedure.

      I think if you just skip to your first string variable that you are passing — “txtName” — if you wrap a sinqle quote (chr(39)) around that one and the other text or date variables, that may be all you need.

      thx
      Pat

    • in reply to: Connect to SQL Server via VBA (2003 SP 3) #1112703

      This isn’t the answer to your problem, but noting your EXEC string, I wonder if you need quotes. The following is just a sample of a call I make. I pass a procedure and a starter date into a module, and then in the module, create the connection and a DAO recordset to hold the rows received. I think if you pass string (or date) parameters, quotes are required — I am not sure.

      Set PatSet = PatsConnection.Execute(“EXEC ” & Chr$(34) & WhatProc & Chr$(34) & ” ” & Chr$(39) & CDate(WhatStarterDate) & Chr$(39))

      Pat

    • in reply to: Filter Excluding Selection excludes nulls too (200 #1112659

      Yeah, this is the null “gotcha,” and believe me, others have ended up in the same boat. My commiseration!
      Pat

    • in reply to: Too many left outer joins (2000/XP) #1112406

      Not sure I have quite got it, but, couldn’t you just add one field that you populate with a plot counter for each plot for each Landowner, and then when you go to output, use as the column title a concatenation of the field name and the plot counter? Would that work?

      Pat

    • in reply to: Running Sum in Group Footer (2003 SP2) #1109479

      Well, I think if Han’s method works fine for the first person, it should work for the next — if you do use the running sum over group. I think (maybe I’m not figuring this out correctly) but I think you really must have a “running sum over group,” so it can restart at zero for each client — unless you want to do that all in code. If the “over group” isn’t working, you might want to re-check your sorting?

      Ignore this that I wrote earlier , but just leaving it in FYI: How to you make the lines invisible — IOW, since you’ve probably got some code to make the line invisible, can you set a public variable at that time that (preventing it from incrementing further while with the current client is the same) and stores the amount you want to display in the group footer, and and then display it? and, upon the client changing, you set this public variable back to zero?

      Pat

    • in reply to: Running Sum in Group Footer (2003 SP2) #1109467

      Did you chose to have the field accumulate as a running sum “over group,” or “over all?”

    • in reply to: Not like Statement working (2003) #1109465

      So that those of us who don’t open attachments can help, can you paste a simplified version of your query to show what you are trying to do to attain the goal of excluding that line?
      thx
      Pat

    • in reply to: One-to-Many Relationship (2003) #1109461

      Monica,

      I would start by creating a query with the information that you want on the report. In order to join all the tables, you need to identify what information in each table can join the two tables together. Once you get that done, you can use the Report Wizard to create a report — you can play around with the variations.

      If you like the form, you can simply highlight it and on the Menubar, chose “File->SaveAs,” and chose, “Report.”

      However, I wouldn’t recommend that until you successfully get the data that you want to display, successfully tied together.

      There are a lot of local businesses offering 1-day classes for beginner, intermediate & advanced users, and I would strongly recommend that. Not only are you doing yourself a favor, you are doing the economy a favor, if you or your business can afford it.

      thx
      Pat

    • in reply to: Gray Header (Access2003) #1109272

      Can’t you make the “backcolor” of your header be gray, (click on your header, or, if no open space, your header bar) and then “lasso” all your labels in the header (select all), click on “properties” if you don’t already have that selected, and make the label backgrounds be transparent? Make sure the “forecolor” of the labels is 0, or some darker gray than you use as the header section background.
      Pat

    • in reply to: Locked Data Message (2003 (11.824.8202) SP3) #1109269

      Sometimes, on a network, I cannot delete an .ldb. It gives me the same error message you get. If I log off & then back on the network I can delete it.

      In addition to what Hans said about copying all the items over to a fresh database, don’t forget to ask click the options box and get any import/export file specifications (no longer available in 2007, I guess), relationships, menu bars, etc.

      Pat

    • in reply to: Problems with fonts (2003) #1106864

      Glad you got it to work, Silverback! I think there are some Windows functions where you can determine what settings the user has, environment-wise, but making it work to modify your product, I just think that would be a massive undertaking . I think that the simplest and easiest suggestion (Han’s and mine) is just to expand the text fields as well as you are able, as well as sticking with the most standard fonts. I still operate in “by guess and by golly” mode as far as resolution, fonts, etc. goes. That works for me because I have a fairly limited (internal) environment to distribute my product to.

    • in reply to: Problems with fonts (2003) #1105383

      YOu might check the “dpi” size. I have two computers, and the same screen resolution, both pointing to the same printer, and yet the fonts display differently on both. I just clicked the “Advanced” tab on my screen propertings “settings” tab, and I don’t know what the heck “DPI” settings are, but on one computer they are “normal,” and on the other they are “large.” MAYBE MORE TO THE POINT — check out the “Appearance” tab in Display properties — on one of my computers, I have checked “large size” for the fonts, on the other, it is normal —

      If you have users that play around with their screens the way I do, with a “by guess and by golly,” that might be part of the issue! I woudn’t want to change their settings, though, they might be very happy with the way they were set.

      As far a printing, though — I have one user where a label caption displays well, but gets chopped off when printing — which I attribute to the printer, in that case. (The solution is simple in that case, though (stretch out the label). It’s wise to be generous with text widths, if you can be, for various reasons.

      Pat

    • in reply to: acFormadd (Access 2003) #1088380

      Hi, Hans,
      I’ll latch on to this message thread, in case anyone else is searching for answers — and you know, I’ve probably re-learned this a few times (must be all that mercury-laden fish I’ve eaten): my “acformadd” call had started failing. At first, I thought it was corruption, and pulled forms into a new database, etc. etc. Then I went searching, and, triggered by this thead, I went back and looked at the “on open” event of the form. It turned out that I was setting an “orderby” at the top of the module (to solve a different problem … ignore this part). I’m using openargs to determine whether the form is showing all, filtered or new, so I moved the “orderby” part so that “New” will not come across it, and voila, it works. I don’t know why an “orderby” would blow a form opened in data entry mode, but apparently, it does — probably because the default settings for the form are the usual “allow Edits,” etc.
      thx
      Pat

    • in reply to: Page numbers within Group Header (2003) #1087422

      Thank you, Hans! once again, you saved the day. As soon as I realized from the link you inserted that pages() was 0 until after the first pass, then, I was just able to check for “if pages() = 0” and prevent some code I had tussled with for a couple of hours here, to get it to work! I only allowed the “lePage” fake page accumulator to run if pages() was more than 0, and it worked. Wow! thx, Pat

    • in reply to: Hyperlinking (All) #1078254

      Thanks, Hans for your reply in “this” post : post 668,760. I also saved this in “favorites for a while. IT WORKED!
      thx,
      Pat

    Viewing 15 replies - 16 through 30 (of 237 total)