User Profile

Collapse

Profile Sidebar

Collapse
patjones
patjones
Last Activity: Feb 4 '14, 11:14 PM
Joined: Jun 27 '07
Location: New York City
  •  
  • Time
  • Show
  • Source
Clear All
new posts

  • I did apply the latest updates, which includes going from SP1 to SP2. I was finally able to accomplish what I needed by creating the transparent areas in Photoshop, saving the image in .PNG format, inserting into a Word document, and then cutting and pasting it from the Word document into the Access report's design view.

    I don't think editing in Photoshop is necessary (it happened to be convenient given the layout of my graphic), but...
    See more | Go to post

    Leave a comment:


  • Image transparency in Access reports during print preview

    Hi everyone! It's been a long couple of years at least since I've posted or contributed here, and I'm real happy to see that the forum is going strong. Hopefully I can start contributing again on at least a limited basis.

    Before that though...it's been a long time since I've been driven as crazy as I have been today. I have an image in a report with transparent parts. The transparency holds just fine in design, layout and report view,...
    See more | Go to post

  • Hi,

    Sorry for the delay, as I've been able to think about this only here and there for a little bit. Maybe you have found a solution, but I want to post what I came up with so that maybe we can get the discussion going again.

    The SQL shown below accomplishes what you want, except that it leaves off the beginning and ending ID's (so in your sample data, 96 and 126 are left out). I need to think a little more about modifying...
    See more | Go to post

    Leave a comment:


  • I think I understand what you need, and I have a SQL query that gets us part of the way there. I'm going to look at it some more later today.
    See more | Go to post

    Leave a comment:


  • patjones
    replied to Problems Dealing with Forms
    That's no problem; let us know how it goes.

    I should add that when you use a look-up table and combo box in this manner, it's commonplace to simply drop the bound value into the stored record (which in your case will go in table 1). What do I mean by this?

    Suppose I build a form to track a vehicle fleet. I might have a look-up table for vehicle make (Ford, Honda, Nissan, etc.) and base a combo box upon that table, which...
    See more | Go to post

    Leave a comment:


  • patjones
    replied to Problem checking textboxes for null
    Correct you are. I got mixed up. When I tried it just now it does indeed capitalize "Value" for you. What it does not do is bring "Value" up in the list of methods for "ctl", an observation that fits in more naturally with what I was trying to say.
    See more | Go to post

    Leave a comment:


  • Basically, you need consecutive records for a lithology to collapse down to one line? So, ID's 108 through 116 would become 108 DDH_1 34.75 89.05 USE?

    I pasted the data into a text file then imported into Excel, saved as an .XLS 2003 file - attached here.

    Pat...
    See more | Go to post

    Leave a comment:


  • patjones
    replied to Problem checking textboxes for null
    I forgot all about that thread, and yet it illustrates many good points.

    One thing that I will say about IntelliSense is that it usually, but does not always, behave as you might expect it to. In the present case, where we defined "ctl" as a Control typed variable and then refer to "Value" as a method of it...IntelliSen se will not capitalize Value for you - presumably because the control type of "ctl"...
    See more | Go to post

    Leave a comment:


  • patjones
    replied to Problems Dealing with Forms
    In order for us help you, I think we need first to clarify the structure of your database. The first thing is to make a distinction between tables and forms. They are two different things. The table stores the data, and the form displays it.

    It sounds to me as though table 2 is what we call a "look-up" table. This is a table with a set of pre-defined records that might populate a combo box or list box on your form, thus...
    See more | Go to post

    Leave a comment:


  • patjones
    replied to Reports don't open...on only some machines
    The network guy over there could not find any issue with the printer. So, I got up off my butt and actually walked over there to get to the bottom of this.

    I took my development copy of the front end with me so that I could run it on the user's computer and step through the code to see where it was hanging. When I did so, I found that it was executing perfectly! Still no report.

    Then I went into the property sheet for the...
    See more | Go to post

    Leave a comment:


  • patjones
    replied to Reports don't open...on only some machines
    Thanks ADezii. The network guy says that there is no problem with the printer. I can't be sure because the two problematic users are in another building across the city; I can't see for myself. But he claims that there is no driver issue.

    Maybe a bit more information will help. The report is sourced by a pass-through query that is in turn sourced by SQL Server tables. When the user clicks the button, Access deletes the previously built...
    See more | Go to post

    Leave a comment:


  • patjones
    replied to VBA code error odbc 3146
    Sharon,

    Error 3146 is a generic ODBC error message. It means that Access cannot properly establish contact with your back end table, and it can occur for any number of reasons. Is dbo_Filestream_ Files a linked SQL Server table? If so, and if the table is properly linked to the back end source, you should be able to open it in datasheet view and examine its contents. If you aren't able to do that, then it means that you need to properly...
    See more | Go to post

    Leave a comment:


  • patjones
    started a topic Reports don't open...on only some machines

    Reports don't open...on only some machines

    Good afternoon,

    I have a 2007 front end that has been distributed to about eight people. Two individuals cannot open the report that is built into the front end. It is programmed to open in print preview.

    At first I thought it might somehow be a service pack issue, as I developed the front end with my SP2 version of Access 2007, and the two users in question have SP1. This turns out not to be the case, as another user...
    See more | Go to post

  • Good morning,

    Sorry for my late reply. Is it the case then that the filters for list and the machine type do work when you select something other than "ALL"? For the dates, Access needs to have them enclosed in "#" signs. Additionally, you can collapse the entire date code down to one line:

    Code:
    strWhereDate = "([TransDate] BETWEEN #" & Me.txtStartDate & "# AND #" & Me.txtEndDate
    ...
    See more | Go to post

    Leave a comment:


  • Is there a particular point where your code stops working?

    Pat
    See more | Go to post

    Leave a comment:


  • "REFA000001 " is not a number, so DMax() + 1 isn't quite going to work. As long as there are always six digits on the rightmost of the string, try this function:

    Code:
    Public Function AddToREF(strREF As String) As String
    
    Dim strNextDigit As String
    
    'Get the next digit
     strNextDigit = CStr(Right(strREF, 6) + 1)
    'Build the string
     AddToREF = Left(strREF, 4) & String(6 - Len(strNextDigit),
    ...
    See more | Go to post

    Leave a comment:


  • Sweet goodness, I was using .DefaultValue all along. When I set things in the property sheet I tend to forget about them. I guess that probably explains why everything is working so well! Thanks.
    See more | Go to post

    Leave a comment:


  • It seems that Dirty is not triggered in my current situation. I set the text box in question to OpenArgs in the property sheet in form design view. The code in the cancel button looks like this:

    Code:
    Private Sub cmdCancel_Click()
    
    If Me.Dirty Then
        If MsgBox("You have entered new information. Cancel new employee addition?", vbYesNo + vbQuestion, "New Employee Entry") = vbYes Then
    ...
    See more | Go to post

    Leave a comment:


  • It turns out that replacing the DeleteRecord line with Me.Undo does the trick...though I'm not entirely sure why.
    See more | Go to post

    Leave a comment:


  • Are you suggesting that I use .DefaultValue in addition to my DeleteRecord line, or eliminate the DeleteRecord altogether? Because when I remove it, that leaves just the line for closing the form - and anything that gets typed into the form gets saved as a new record, because it's a bound form. So I reason that something has to be put in the code to tell Access "no, I don't want to save this information"....
    See more | Go to post

    Leave a comment:

No activity results to display
Show More
Working...