• WSGARYPSWANSON

    WSGARYPSWANSON

    @wsgarypswanson

    Viewing 15 replies - 31 through 45 (of 1,725 total)
    Author
    Replies
    • in reply to: list box in form (access 2007) #1816586

      Rick,

      Your report should show you the multiple pains separated by comma’s if the data is setup as multivalue. I am not sure what the problem is you are having. Can you attach a stripped down version of your database?

    • in reply to: list box in form (access 2007) #1816575

      Rick,

      I stopped using switchboards a long time ago as I did not find them very useful. In prior versions of Access there was a limit to how many command buttons that could be used to trigger actions such that you would find people jumping from switchboard to switchboard.

      You might find it much easier to create a form and then insert command buttons to do what you want. If you use the wizard, you could insert a command button that opens the report. FWIW, I would recommend staying away from switchboards. If you use a form, you can have the form open when the database opens so it looks like a switchboard.

      Now to answer your question. The recordsource on the report is qryVisitsDate. As there is no object in the database with this name, you get the error message when trying to open the report as the recordsource does not exist.

      HTH

    • in reply to: list box in form (access 2007) #1816568

      Rick,

      – Open your database and close all open forms.
      – Open your sbfVisits form in design view
      – Delete the current pain combo box
      – Open the field list
      – Select the Paid ID field and drag it into the form and the multivalue list will work as your properties on the Pain ID in the main table are set as a lookup and allows multivalues.

      You probably created the original combobox before setting your properties to allow for a multivalue field list so the combobox retained the original settings.

      HTH

    • in reply to: list box in form (access 2007) #1816566

      Rick,

      I have been following this string of posts and you basically have two options if you want to sore multiple pain values for a visit.

      1. Using the Multivalue list, select the pain or pains a person has per visit and store that in the visit table. (I have attached your database modified slightly that does this) This stores your selected items in one field with commas between each selection. Open your patient form to see this.

      2. Create a new table – lets call it TablePains. Fields are ID, VisitNumber, Pain. Link to visit table as a one to many on the visit id. Use a multi select listbox and after selecting the “pains”, use code to go though the data and write it to the table. This way, each selection is stored as a separate value linked to the visit.

      Anyway, the attached database shows an example of number 1. HTH

    • in reply to: list box in form (access 2007) #1816556

      Rick,

      One other question. Your form that has the listbox for pains is tied to the main patient form. Wouldn’t you want this listbox that selects pains to be tied to not only the patient but on a particular visit as I would assume that a patient could have different symptoms or pains on different visits.
      The listbox for pains should be tied to the vist table. You might want to move this listbox to the visits form. Just something to think about.

    • in reply to: list box in form (access 2007) #1816555

      Rick,

      John brings up some good points. In looking at your current design, you input patient data into TblPatients. Then you use a one to many relationship to track visits in the table named Visits that is linked back to the patient table via the SocSecNo. Your table PainLevel is used as a lookup to select the PainLevel of the patient for the current visit.

      If I understand your request, you want the ability to select one or many Pain Levels for the current patient visit and want to store the data selected. (Correct?)

      The question is how to do this? Do you want to use a MultiValue field as the selection that stores the data in a string as choice 1, choice2, choice3? I would not do it this way as it would then be a little more difficult to get a count on patients with a particular pain as the stored data is stored as part of a string. If using a multiselect listbox, you can loop through the values and store the data in a table that links back to the visit table via the visit number and store each pain as a separate value. It would then be easy to use the “pains” selected for further analysis or querying.

      Anyway, back to your question. How do you want to obtain the data – via a multivalue listing that stores the data in a string or a multiselect listbox that would store the individual records in a new table linked to the visit as a one to many relationship?

    • in reply to: list box in form (access 2007) #1816551

      Rick,

      Check out the following link for a review on creating multivalue fields. HTH http://office.microsoft.com/en-us/access/H…=CH100645681033%5B/url%5D

    • in reply to: list box in form (access 2007) #1816550

      John,

      After re-reading the post, you are absolutely correct. I am going to post a link to the original post that has directions on how to use multivalue fields.

    • in reply to: list box in form (access 2007) #1816547

      The first step is you are going to need to modify the listbox to a multi-select listbox to be able to select multiple values.

      In the form design view, select the properties of the listbox, go to the other tab and set the Multi Select row to extended. This permits you to select multiple values in your listbox. You still need to determine how to get the data where you want.

      I am, unfortunately, lost in your description of where you want to write the selections to. Once you make your selections, do you plan to store them in a table linked to the patient ID or other?

      This should give you a start. If you search the forum on multi select list boxes you will find many examples of how to get the data selected and store them. Post back if you are stuck.

    • in reply to: Incorrect start calculation (MSP 2003/no SP installed) #1119727

      Michelle,

      I am going to assume that you checked and your tasks have a standard finish to start relationship without any lags built into the relationship. There could be any number of items that could cause your issue but without specifics it will be hard to pinpoint.

      1. Check to make sure you dont have any lag on your relationships.
      2. Check your calendars to make sure they are not set for 24 hour workdays. *
      3. You indicate you have not loaded any service packs. 2003 has several service packs which I would recommend installing even if has nothing to do with your problem as they fix many issues.

      * My guess is it would have to do with the calendars (either base or resource) if this effects many tasks. How are your tasks setup – effort driven, fixed, etc. (Something else to look at)

      My recommendation is to load the service packs to see if the error corrects itself. If not, check your calendars. If you still have no luck, post back and we will see if we can help.

    • I am not sure you can connect directly to project but should be able to save your project to a project database and connect to that. The issue will then be you are able to access the tables but how to get useful information out of it. There is typically a white paper available that reviews project and the table structure so you can get or use a query to derive useful information and use that as the data source. If you go this route, the tables that I have found to be most useful are MSP_TASKS and MSP_TEXT_FIELDS.

      Another option would be to run or create an export map to export data to a .csv file or other format readible by crystal to use as the data source. This is a little easier.

      What data are you trying to access?

    • in reply to: Update Links Macro (Project 2000/SR1) #1113276

      Tim,

      My apologies for taking so long to get back to you. I did review your file, however, I was unable to find your version of Project or figure out how to do what you want in other versions. I wont say it cant be done but I am unable to figure it out.

    • in reply to: query – 125% of poverty (2003) #1110985

      Melanie,

      You said that you have a query that gets the total number of people (lets call the field TNP) and I assume you have their total income (call the field TI)

      You could do the following in your query to generate your yes/no field: (Assumes TI and TNP are available fields in the query)
      IIF(TI > (10400 + (3600 * ([TNP]-1))),-1,0)

      Basically, this says if the Total Income is greater then the HHS Calculation then yes else no. You can calculate your HHS guidelines by the equation shown. 10400 + (3600 * ([TNP]-1))

      HTH

    • in reply to: Exporting Field Data Types (2003) #1110967

      Hayden,

      Try the following.

      Select Tools Analyze Documenter
      Select Tables Tab and Select the tables you need data on
      Select Options, Include for tables selections are unchecked, Include for Fields middle radio button, Include for Indexes as needed and press OK
      Select OK to generate the report
      With the report open, Select File Export, Choose Excel
      This is not pretty but will get the data to excel.

      HTH

    • in reply to: Update Links Macro (Project 2000/SR1) #1110822

      Tim,

      I currently have access to Project 2003 and 2007. I think I may have a version of 2000 running somewhere. I was able to find some old Project 2000 reference books but they dont even review Hammock tasks. I will admit I am a bit rusty as I have not done any scheduling for a few years. However, if you can post a simple stripped down version or make a very small project with at least two hammock tasks in it (using 2000) I will see if I can figure out a way to get the code to update the tasks. (Of course, this assumes I can find a working version of 2000 as well). (I hate being stumped!)

    Viewing 15 replies - 31 through 45 (of 1,725 total)