Jump to content

CeeEssGee

Members
  • Posts

    28
  • Joined

  • Last visited

About CeeEssGee

  • Birthday 07/31/1984

CeeEssGee's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Yeah.. I'm not sure about this export function. I've fiddled around with it a bit, but the main reason I gave up was because it couldn't directly export to an excel file. So.. I can export to a .tab file, and then import that (from excel?) to an excel file, and then import that excel file to a .fm7 file? Oookay, that sounds like fun.
  2. Hmm, well, I guess at least I know it's a bug now, so I don't have to wrack my brain trying to solve it. Is there any way to put serial numbers in to excel, then? IE, make a calculation for every cell in a column to be (starting number) + row number? That would make this so much easier.. I think I'm going to use a rusty spoon as a deadly weapon otherwise.
  3. Argh, this is driving me nuts. I contracted a few people to put in data on to a spreadsheet in Excel, and now I'm trying to import this data in to the "LawCases" database, and for some reason, I'm able to import them fine straight from the excel file, but when I try to import them from another .fp7 file that I have imported the excel data in to (in order to mess around with the serial numbers easily), the damned thing keeps giving me this message! I'm able to do it from the "Clients" layout, and the BoxesMatters layout, for some reason, but not any of the others.. Please help, this could take days if I'm not able to mess around with serial numbers on a seperate file (this one is way too complicated).
  4. Anyone? Nothing seems to work.
  5. Bleh, this is really annoying. I can't figure out why these account names won't show on the grouped report..
  6. Ah, that helps, thanks! Whenever I make the summary reports though, it doesn't register the account names at all. Its in preview mode, the values and descriptions are all there, but there is a spot for account names and nothing there (this is from expenses). Also, how would I be able to filter this preview to only preview for that specific monthly report?
  7. I'm working on a program for our office to make balancing the Visa a bit easier. Its fairly simple, and doesn't need many protections from user error, although I guess in the future a reliable annual report would be nice. This is what I have so far, but the one thing I am having trouble with is providing subtotals (For GST, Post, and Total) for each "category", being the account names. The post amount is the amount we need to pay, the GST is the tax (that we don't have to pay; it's the 8% PST tax that we do have to pay). Any ideas how I can get this to work, easily? I don't want to have to flip between three different windows just to put in an account name (like my "Law Office Database"), but to be able to just put it in on a quick drop down list. BalanceVisa.zip
  8. Okay, I fixed it up with what you did on the last file, and now I'm pretty much ready to go. I put in most of our database, and it seems to be working fine. One problem though, is that when I add an alias to a client, if I look under the alias, it doesn't have that client listed under it's aliases. For example, if Bill has an alias Tom, and I add that, if I go to Bill's record, it will show an alias of Tom. If I go to Tom's record, though, it will not show that his alias is Bill. How do I fix this? Can this be solved by a few more script steps, or do I need to make a new TO? LawCases9.zip
  9. I haven't seen your latest attachment yet, but I'm about to open it. Here's the one that I made (updated to take in to account aliases). LawCases8.zip
  10. Yeah, this is a lot cleaner than mine, and actually works (which is definately a bonus). I really wish I could figure this stuff out, though. I finally understood how you are using the global variables on Friday, heh. Now I'm going to concentrate really hard, and try to figure out how to make the aliases function . Is this database really complex? Moreso than most? Oh, also, how would I go about putting a display of the range of Closed "IDs" in each box? That would be *very* useful for the list view. I'd have to somehow find the minimum value of all related records, and then a - (or equivalent), and the maximum value, right? (Edit: Nevermind, I figured that one out)
  11. Here's what I've done with it to this point. It's not pretty, and it doesn't really work, but it does incorporate nearly everything I'm aiming for. (I'm still working on it, especially with having the scripts that join the alias to clients, and boxes to closed to cases) LawCases6.zip
  12. I know, but, our storage company is very anal about this and won't let us chose the numbers on the boxes. This is fine though, because so far they have been very good as far as service goes. So, it would be very silly to have data different on the boxes, than the database, because we use the database to send in for the physical boxes, so it needs to be consistent. So, yeah, I do need these arbitrary Serial IDs in the database, but there's no reason anyone should actually know what they are (except for me, when I want to alter the matching IDs on the join tables.)
  13. Well, I could always put in a boxes table. Going to try that in the morning.
  14. Well, I'm still having a problem with the message "case is already assigned to another box". What's causing this? I see the code, but.. it doesn't have a box value yet. This happens whenever I try to create a new box and add it to there.
  15. The ClosedID isn't really an ID as we have been using, it's more a number. A value which is usually increasing everytime we close a file, but is subject to human error (and thus, we cannot use it as a consistent ID). The same goes for the OpenID, and BoxID. I'll call all of those -num, rather than -ID to make things easier. When a case is closed, it is always immediately boxed. We usually fit about 5-20 cases per box. But, the cases can switch boxes frequently, and we don't know all of the locations of the cases, heh. Trust me, if you think this is confusing, you should see our file card system! (Or rather, you probably shouldn't ) Oh, and the ClosedID in cases is a mistake. It's leftover from when I was using it on the same table.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.