Search results

  1. P

    C & R

    Yes, when you replace it always, you do not need to check the version. I do NOT replace it always, hence the version check. I only replace when needed, in the multi-user systems. For the single-file configuration, I know there are other ways to do this, and I understand that a split system...
  2. P

    C & R

    No - resetting the starting number of the autonumber field is what (apparently) creates a new column, while leaving behind some hidden dregs of the former one. C & R clears out such debris. Reset the start enough times (~255) without C& R, and you get the "too many fields" error. Try putting...
  3. P

    C & R

    Ah, yes. Thank you. I have looked at that mechanism, and it doesn't quite suit my purposes. I have two main 'types' of customers. One is a multi-user environment, talking to a SQL Server backend. There of course I have separate front ends, but I use a version number. When an FE opens, it...
  4. P

    C & R

    "No meaning" is only one way to use an autonumber field. I was using it as a sequence number - seemed a handy, no-code way to get sequential numbers. And it does do that, very nicely. There are no other actions that mess with this temp table, so I have no problems of missing numbers or any of...
  5. P

    C & R

    No, you misread my post. I did not overrun the maximum allowable number IN an autonumber field - I reset the autonumber field to start at 1 again. The clods at MS somehow coded this action to not actually reset the numbering, but instead create a NEW autonumber field in the same table, while...
  6. P

    C & R

    No bloat, no automated C&R. I have one temp table in which I reset the autonumber field. I never ran into it during my testing, and the user never encountered it in the 16+ years he's been using the app, until yesterday. He was pounding furiously on one specific function that used that code, and...
  7. P

    C & R

    Is there any way to detect when a database was compacted on its previous close?
  8. P

    Win64 version crashing

    I got everything working, tested it all on every machine I have available, decompiling and recompiling on every machine, and testing that freshly compiled version on every other machine. All worked perfectly everywhere, so I installed it on the customer's machine and returned it to him. Customer...
  9. P

    Win64 version crashing

    Well, then he's better at this than I am. I looked at all those things, and tried all sorts of things, and failed. It's hard to make much progress when you don't really understand what the calls do, what the exact problem is, and every failed attempt crashes the app. Xavier is much better, or...
  10. P

    Win64 version crashing

    Well, I tried the complete package and it works perfectly on my machine, so now I need to get to work porting the code into my app. Maybe I'll even figure out along the way exactly what the problem is with my current setup. Many thanks - if you ever make it to Prague, the beers are on me.
  11. P

    Win64 version crashing

    Jesus - WHERE did you get this? I'm going to try this right away. If it works, I am forever in your debt. Thank you.
  12. P

    Win64 version crashing

    1. Okay, I didn't realize that had been changed, but it's still not many for my purposes in this app. There are 679 squares in the grid that can potentially contain a symbol, and some instances will have most or maybe even all of them filled. And that is even before the lines to form the grid...
  13. P

    Win64 version crashing

    Some stuff you cannot, some you can. But what I'm running into crashes either way, although of course, I cannot tell if it might be crashing differently when I step it. When I step it, the crash comes at the point of calling the timer routine, and it crashes the same way regardless of whether I...
  14. P

    Win64 version crashing

    Thank you, I'll see what I can get done with that converter. Back to work. I admit, I had not thought of using Access's built-in stuff. The PictureBox class does a great deal, but I don't need most of the functionality that Stephen put into it, and have removed the code that never got called. I...
  15. P

    Win64 version crashing

    Yes, that was me. I have been working on this for a while. The problem cropped up, then became irrelevant because of some other circumstances, but now it's serious. I did look at those links, both back then and again recently, when this showed up again. They do provide a great deal of...
  16. P

    Win64 version crashing

    Well, maybe, but that is where it crashes. I do have some custom images on the ribbon that serves that form. There are three principal forms in the app, and the one using the picture box class also has some custom images in the ribbon - the only one of the three to have either. But when I bypass...
  17. P

    Win64 version crashing

    Who is that someone you think you know?
  18. P

    Win64 version crashing

    I'm not sure about all that. There is a good deal of stuff in his code that I flat do not understand. This is one of those things. I have no idea why I need a timer at all, when what I am doing is painting a screen image, but I doubt he put it in just for a lark. The code works in 32-bit...
  19. P

    Win64 version crashing

    Why should it be public? Lebans wrote it as private and it has been working that way without a hitch for at least fifteen years. In any case, I just tried making it so, and no difference - still crashes. And I am trying very hard to track down all the instances of data types, but nothing yet...
  20. P

    Win64 version crashing

    Ah, thank you. It is, though - it's the very next routine after this AutoShutDown. Private Sub TimerProc(ByVal hWnd As Long, ByVal uMsg As Long, ByVal idEvent As Long, ByVal dwTime As Long) ShutDownGDIP End Sub One of the things I've tried is changing the parameters here to LongPtr and...
Back
Top Bottom