Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error occurs when saving files in Visual dBase 5.5 #1171

Closed
fzhwenzhou opened this issue Jul 9, 2022 · 3 comments · Fixed by #1172
Closed

Error occurs when saving files in Visual dBase 5.5 #1171

fzhwenzhou opened this issue Jul 9, 2022 · 3 comments · Fixed by #1172

Comments

@fzhwenzhou
Copy link

fzhwenzhou commented Jul 9, 2022

Describe the bug
When creating a new table and saving it, the winevdm firstly pops up many memory errors. If you click "continue" for many times, it will finally display the "Save" window. But after you input the name of the table and click "OK" it will pop up another window indicating "the engine is not initialized". And the file is not saved. Please help to solve this problem. Thanks.

Expected behavior
No warning or error is displayed and the file is saved correctly.

Environment (please complete the following information):

  • OS: Windows 11 Professional (22000.778)
  • Winevdm Version 2314
@fzhwenzhou
Copy link
Author

fzhwenzhou commented Jul 11, 2022

Yes it works exactly, but the dialog has another bug: If I change the filename from "*.dbf" to something meaningful, and then change the drive (for example from C: to D: , or only click on it but not really change the drive), the filename goes back to "*.dbf". I wonder whether it is winevdm's problem or not. Thanks.

@cracyc
Copy link
Contributor

cracyc commented Jul 11, 2022

This doesn't happen for me on Windows 10. It does happen if I click on the file type combo box which makes sense.

@fzhwenzhou
Copy link
Author

This doesn't happen for me on Windows 10. It does happen if I click on the file type combo box which makes sense.

Oh sorry maybe I mean this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants